help with ls please Post: 9420

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers help with ls please Post 9420 by Perderabo on Friday 26th of October 2001 10:29:09 AM

10-26-2001

Administrator Emeritus

Sheesh, where to start?

That ls you did is putting the link count as the first thing on the line. In effect, you sorted on link count.

I've never heard of xfs_repair but it sounds like fsck. The lost+found directory is used by fsck as a place to store inodes that are orphaned. The orphaned files are linked into the lost+found directory with the name being set to the inode number.

With most current filesystems, directories grow but do not shrink. This is exploited by fsck. The lost+found directory has empty slots already allocated. There typically is a script called mklost+found to rebuild it if it is removed.

Since fsck is running and we have located orphaned files, there clearly is file system damage. Under these circumstances, the list of free blocks in the filesystem should not be trusted. That's why lost+found must have space available, fsck cannot safely find a free block at this point in time. One of the last thinks fsck will be is to rebuild the free list. This also simplifies the code required to write fsck.

Perderabo

View Public Profile for Perderabo

Find all posts by Perderabo

LEARN ABOUT OSF1

fdmns

fdmns(4)						     Kernel Interfaces Manual							  fdmns(4)

NAME

       fdmns - contains file domain names and devices

DESCRIPTION

       The  fdmns directory ensures access to file domains by providing symbolic links to every volume in the file domain.  The mkfdmn, rmvol, and
       addvol utilities automatically manage the fdmns directory.  Each file domain is described by its own subdirectory within the  fdmns  direc-
       tory.

       Back  up  the fdmns directory structure regularly using the vdump utility or any other backup utility (dump, tar, cpio). If the contents of
       the fdmns directory are deleted or corrupted, restore the directory from your most recent backup tape.  You must  also  restore	the  fdmns
       directory after installing a new version of the operating system.

       Always  keep  a hardcopy record of each file domain and its associated volumes in case a backup copy of the fdmns directory is unavailable.
       If you have a record, you can reconstruct the fdmns directory structure. The following is a sample fdmns directory:

       total 2 drwxr-x---     2 root	system	  512 Nov 24 18:35 scratch/ drwxr-xr-x	   2 root    system    512 Nov 24 18:35 usr/

	./scratch: total 0 lrwxr-x---	  1 root    system    10 Oct 23 15:13 dsk10c@ ->  /dev/disk/dsk10c  lrwxr-x---	   1  root    system	10
       Oct 24 11:33 dsk11c@ -> /dev/disk/dsk11c lrwxr-x---     1 root	 system     9 Oct 13 18:29 dsk8c@ -> /dev/disk/dsk8c

	./usr:	total  0 lrwxr-x---	1 root	  system     9 Oct 24 10:52 dsk2g@ -> /dev/disk/dsk2c lrwxr-x---     1 root    system	  9 Nov 24
       10:35 dsk9c@ -> /dev/disk/dsk9c

RESTRICTIONS

       Do not remove or modify the contents of this directory.	If the fdmns file becomes corrupted, you can no longer access (or mount) any file-
       set in the file domains.

SEE ALSO

       advfs(4), vdump(8), mkfdmn(8), vrestore(8), showfdmn(8)

																	  fdmns(4)