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 PHP

systemd-volatile-root.service

SYSTEMD-VOLATILE-ROOT.SERVICE(8)			   systemd-volatile-root.service			  SYSTEMD-VOLATILE-ROOT.SERVICE(8)

NAME

       systemd-volatile-root.service, systemd-volatile-root - Make the root file system volatile

SYNOPSIS

       systemd-volatile-root.service

       /lib/systemd/systemd-volatile-root

DESCRIPTION

       systemd-volatile-root.service is a service that replaces the root directory with a volatile memory file system ("tmpfs"), mounting the
       original (non-volatile) /usr inside it read-only. This way, vendor data from /usr is available as usual, but all configuration data in
       /etc, all state data in /var and all other resources stored directly under the root directory are reset on boot and lost at shutdown,
       enabling fully stateless systems.

       This service is only enabled if full volatile mode is selected, for example by specifying "systemd.volatile=yes" on the kernel command
       line. This service runs only in the initial RAM disk ("initrd"), before the system transitions to the host's root directory. Note that this
       service is not used if "systemd.volatile=state" is used, as in that mode the root directory is non-volatile.

SEE ALSO

       systemd(1), systemd-fstab-generator(8), kernel-command-line(7)

systemd 237													  SYSTEMD-VOLATILE-ROOT.SERVICE(8)