ok - a new section in my little series:
just shutdown the machine again and repair_xfs'ed them to check -
root filesystem again had small problems (but i think this will be
fixed soon when the umount code is in) and the other partition had
no problems at all - so everything is best
also this week i had increased the load of the system a bit - it
is now running the squid for our company (~50 users, 500mb cache)
and a dummy news server (inn) with a feed of about 4000 articles
per day and 30 simulated users reading away all articles all few
minutes) - everything is running on xfs and i had no problem so
far
ok - compiled a fresh kernel and will come back next week - but so
far xfs looks really good ...
one thing i noticed at the repair_xfs is the folowing:
...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- ensuring existence of lost+found directory
- traversing filesystem starting at / ...
rebuilding directory inode 128
- traversal finished ...
- traversing all unattached subtrees ...
- traversals finished ...
- moving disconnected inodes to lost+found ...
...
i got that "rebuilding directory inode 128" on both / and the other
partition - is that normal or an found (and maybe fixed) error in
the filesystem ?
t
--
thomas.graichen@xxxxxxxxxxxxx
technical director innominate AG
clustering & security networking people
tel: +49.30.308806-13 fax: -77 http://innominate.de
|