Thomas Graichen <news-innominate.list.sgi.xfs@xxxxxxxxxxxxx> wrote:
> looks better - so it looks like that xfs maybe have some problems
> running as / fs ? - ok will keep posting my observations over
> time ...
just noticed that even running xfs_repair again (and again :-) over
the fs with problems results in the following:
[root@january /root]# /usr/src/xfs/cmd/xfs/repair/xfs_repair /dev/hda5
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- clearing existing "lost+found" inode
- marking entry "lost+found" to be deleted
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
Phase 5 - rebuild AG headers and trees...
- reset superblock...
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 ...
disconnected inode 7340166, moving to lost+found
disconnected inode 7340168, moving to lost+found
Phase 7 - verify and correct link counts...
done
[root@january /root]#
will update the kernel now and see what the next week brings :-)
t
--
thomas.graichen@xxxxxxxxxxxxx
Technical Director innominate AG
Clustering & Security networking people
tel: +49.30.308806-13 fax: -77 http://innominate.de
|