> From: selinux-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:selinux- > bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Daniel J Walsh > Sent: 01 February 2012 14:02 > On 01/31/2012 05:06 PM, m.roth@xxxxxxxxx wrote: > > Y'know, folks, fsck -c gives you a clue that not only is it > > running, but a vague feel for how much longer it'll be. > > .autorelabel, esp with several 2TB drives in a system, gives > > screens and screens and screens of asterisks, with no clue if it'll > > *ever* finish (which matters, when I'm going to be leaving soon, > > and it needs to be up for an overnight backup....) > > > > mark > > > > -- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx > > https://admin.fedoraproject.org/mailman/listinfo/selinux > > > > > Give me a mechanism to know how many files are on the file system and > I might be able to give you an idea. > > Basically this is doing a > > find / > > I don't think there is a way to know how many files are left. Poking around with a couple of commands gave me some results: # e2fsck -nv /dev/mapper/slsvg-usrvol 91208 regular files 11779 directories 0 character device files 0 block device files 0 fifos 20300 links 642 symbolic links (642 fast symbolic links) 0 sockets -------- 123929 files # find /usr -xdev | wc 123929 123929 7687890 I wasn't able to get good timings, because even running the e2fsck command seemed to help the find command run faster. I'd expect though that either of those commands will complete more quickly than the fetch-the-name;fetch-its-attribute;get-the-context;get-the-correct-context;compare-them;write-the-new-context loop. Whether that would be sufficiently more quickly to justify the extra overhead time in setting it up is an experiment I don't have the leisure time to conduct at the moment ;-). Moray. “To err is human; to purr, feline.” -- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/selinux
