Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!munnari.oz.au!manuel!cmf851
From: cmf851@anu.oz.au (Albert Langer)
Newsgroups: comp.unix.sysv386
Subject: Re: fsck Recovery From Crashes
Keywords: inode file directory lost+found
Message-ID: <1991Jun6.070129.4796@newshost.anu.edu.au>
Date: 6 Jun 91 07:01:29 GMT
References: <1074@camco.Celestial.COM> <1991Jun4.020353.11910@newshost.anu.edu.au> <4Jun91.144729.1340@franklin.com>
Sender: news@newshost.anu.edu.au
Organization: Computer Services Centre, Australian National University, Canberra, Australia.
Lines: 31

In article <4Jun91.144729.1340@franklin.com> bill@franklin.com (bill) writes:

>: I have an awk script adapted from one by Tony Moraes, which
>: converts an ls -alR listing into the same style as "find".
>: It would be easy to use ls -ailR and include the inode number
>: in the output and sort on that.
>
>Urk. Why go to all the hassle?
>
>	find $dir -mount -print | xargs ls -di
>
>gets you inode,file in a neat listing.

True. The awk script was developed for processing the output of
ftp ls commands where it is only possible to run ls but not find.
(It also processes dates into a uniform sortable format instead
of the different handling of recent and ancient dates by ls -l).

While it would not be worth writing for the inode directory, I
imagine it is probably more efficient than running ls on each
small batch of file names with xarg.

I also suggested the find -ls option which would be yet more
efficient where available and ff which would be the
most efficient.

Don't forget he's planning to run this every day on every file.

--
Opinions disclaimed (Authoritative answer from opinion server)
Header reply address wrong. Use cmf851@csc2.anu.edu.au