Sandon,
Thanks for the response :-) I'm guessing the volume size is the problem here
because I think my journals stopped working when I switched from 1 to 1.5 TB
drives (12T -> 18T volumes).
> The 8 hour fsck amazes me though, how many inodes are you running on that
> thing?
Here are the stats for the volume where fsck took 8h 37m...
Filesystem Inodes IUsed IFree IUse%
/dev/md12 4,294,967,295 11,520,071 4,283,447,224 1%
> My fsck takes only ~10 minutes with 6 mililion inodes (I think the inode count
> effects it the most).
Either you're getting better disk performance than I am or some other factor
effects
fsck run time.. How many files do you have? The volume that took 8+ hours has:
19027657792 kilobytes total disk space.
5601979 kilobytes in 513655 directories.
14702061342 kilobytes in 11006413 user files.
0 kilobytes in extended attributes
0 kilobytes in access control lists
14181225 kilobytes reserved for system use.
4317017204 kilobytes are available for use.
> PS: multi-petabyte data farm? JFS? software raid? backblaze?
Yep, that's us :-)
Tim
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
