.fsadm

[roger_114]

I've noticed on one of our servers that the lost+found directories contain the following:
-r-------- 1 root sys 0 May 6 2004 .fsadm

Why is this file (.fsadm) in these folders)?

Thanks

[Robert-Jan Goossens · Accepted solution]

Hi,

If you use fsadm to extend a filesystem, fsadm will lock this filesystem with a lost+found/.fsadm lock file. So this looks like a failed attempt to extend the filesystem.

Hope this helps,
Robert-Jan

[Florian Heigl (new acc)]

Hmmm.. I don't quite remember what it's function is, but I'm used to it being there.
If You run mklost+found I think it's also placed there again, so it has *some* function, but where I now looked, it doesn't exist.

have a look at the following snippet from the mklost+found man page:
DESCRIPTION
The mklost+found command creates a directory named lost+found in the
current directory. It also creates several empty files which are then
removed to provide empty slots for the fsck command (see fsck(1M)).

I just tried it, but no .fsadm stayed.

I hope someone has better educated information on this...

[TwoProc]

I believe that I've also seen that after doing a reorg of an online jfs filesystem...

[A. Clay Stephenson]

It's the lock file for the fsadm command. Man fsadm_vxfs for details. A zero length file (or no file) indicates no fsadm is running on the filesystem. Leave it there and certainly do not remove the loct+found directory.

[Stuart Abramson]

As noted above, it's the fsadm lock file.

BTW, if you remove the lost+found directory, fsadm will no longer work. Also, I think that other features of online JFS won't work, like extend or reduce on the fly.

[James George_1]

Hi

when you do an fsck , it also dumps some thing in our lost+found directory ..

Rgds / AJmes

[Florian Heigl (new acc)]

James - if fsck dumps something in lost+found then Your fs was a bit broken :)