Operating System - HP-UX
1834713 Members
2434 Online
110069 Solutions
New Discussion

New File System on HP-Ux V11.00

 
SOLVED
Go to solution
Jean-Michel GUY
Occasional Contributor

New File System on HP-Ux V11.00

Hello,

I have added a new FS on my server. It's a journakized FS (VxFS).
Under the mount directory there is a directory called "lost+found".

Do I have to create a file named .fsadm in the lost+found directory ?!

Thank You
Need backup !
5 REPLIES 5

Re: New File System on HP-Ux V11.00

No

This is from the man page for fsadm_vxfs :

fsadm uses the file .fsadm in the lost+found directory as a lock file.
When fsadm is invoked, it opens the file lost+found/.fsadm in the root
of the file system specified by mount_point. If the file does not
exist, it is created. The fcntl(2) system call is used to obtain a
write lock on the file. If the write lock fails, fsadm will assume
that another fsadm is running and will fail. fsadm will report the
process ID of the process holding the write lock on the .fsadm file.


HTH

Duncan

I am an HPE Employee
Accept or Kudo
S.K. Chan
Honored Contributor

Re: New File System on HP-Ux V11.00

Short answer is no. When fsadm is used to extend a filesystem for example, it'll create a lockfile in lost+found directory. You would have problem with fsadm if lost+found does not exist.
Bill Hassell
Honored Contributor

Re: New File System on HP-Ux V11.00

lost+found MUST exist on every locally mounted filesystem where disk corruption might occur (this is hfs as well as vxfs but not cdfs). lost+found is where orphaned inodes are placed when a directory is corrupted and a name is no longer associated with a set of inodes.

If it is removed, the system will function until a crash or some other corruption forces fsck (filesystem checker) to run. fsck cannot fix any lost inodes as there is no place to put them. Always make sure lost+found is on all locally mounted, writable filesystems.


Bill Hassell, sysadmin
Deshpande Prashant
Honored Contributor

Re: New File System on HP-Ux V11.00

HI
When fsadm is invoked next for any file system (VxFS) maintenance, it'll create a lockfile in lost+found directory. You need not create it manually.

Thanks.
Prashant.
Take it as it comes.
Roger Baptiste
Honored Contributor
Solution

Re: New File System on HP-Ux V11.00

<>

No! When a FS is created it created the
lost+found directory for FS maintenance reasons. You will be better off leaving that directory untouched. .fsadm is a lock file which gets created and removed as per the execution of fsadm command.

HTH
raj
Take it easy.