hmm, on Sat, Jun 02, 2012 at 10:44:22AM +0000, Christian Weisgerber said that
> Otto Moerbeek <[email protected]> wrote:
>
> > > >I just fsck'ed a 2.7TB filesystem in 1 minute, 43 seconds.
> > > >61% full, 447166 files.
> > >
> > > What CPU and how much RAM? SATA2 or 3?
> >
> > Even more important: block size, fragment size, # of inodes?
>
> Default values all the way. 64k/8k.
>
> Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
> /dev/sd1d 2.7T 1.6T 1.0T 61% 447167 91273535 0% /export
>
> Watching this with top, I see fsck_ffs grow to a measly ~44 MB
> resident size.
these must be some really nice disks :]
for example only a 200G slice (also 64k/8k) of music/film/picture
collection (not even full yet) on a notebook disk (5400 RPM) takes ages:
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/sd0d 217G 153G 63.5G 71% 44815 7197423 1% /data
$ time sudo fsck -f /dev/sd0d
** /dev/rsd0d
** File system is already clean
** Last Mounted on /data
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
44815 files, 20076091 used, 8329340 free (13748 frags, 1039449 blocks, 0.0%
fragmentation)
4m58.26s real 0m22.50s user 0m7.28s system
i am more than curious about your amd thread, i am trying to get
rid of fsck times by creative disklabeling and mounting read-only...
-f
--
there are 3 kinds of people: those who can count & those who can't.
