System is Debian Sarge. Kernel is 2.4.27-2-386
I'm quite sure it's not hardware fault. Some people told me it was not a
good idea to use 2.4 with xfs. They are probably right, but now question is
how to get my files back.
xfs_check says nothing
xfs_check -v produces 3045M output of this kind
------------------------
setting block 0/0 to sb
setting block 0/1 to agf
setting block 0/2 to agi
setting block 0/3 to agfl
setting block 0/5 to btbno
setting block 0/7 to free1
setting block 0/8 to free1
setting block 0/9 to free1
setting block 0/10 to free1
setting block 0/11 to free1
setting block 0/16 to free1
setting block 0/17 to free1
setting block 0/18 to free1
setting block 0/19 to free1
setting block 0/20 to free1
...
------------------------
xfs_repair says
------------------------
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
XFS: totally zeroed 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
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 42
- agno = 43
- agno = 44
- agno = 45
- agno = 46
- agno = 47
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
- agno = 60
- agno = 61
- agno = 62
- agno = 63
- 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
- deleting existing "lost+found" entry
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- agno = 24
- agno = 25
- agno = 26
- agno = 27
- agno = 28
- agno = 29
- agno = 30
- agno = 31
- agno = 32
- agno = 33
- agno = 34
- agno = 35
- agno = 36
- agno = 37
- agno = 38
- agno = 39
- agno = 40
- agno = 41
- agno = 42
- agno = 43
- agno = 44
- agno = 45
- agno = 46
- agno = 47
- agno = 48
- agno = 49
- agno = 50
- agno = 51
- agno = 52
- agno = 53
- agno = 54
- agno = 55
- agno = 56
- agno = 57
- agno = 58
- agno = 59
- agno = 60
- agno = 61
- agno = 62
- agno = 63
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 / ...
- traversal finished ...
- traversing all unattached subtrees ...
- traversals finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done
------------------------
----- Original Message -----
From: "evilninja" <evilninja@xxxxxxx>
To: "kempston" <kempston@xxxxxxx>
Cc: <linux-xfs@xxxxxxxxxxx>
Sent: Sunday, November 27, 2005 6:22 PM
Subject: Re:
kempston schrieb:
Today i found strange errors on my xfs drive: some files were locatable
only in ls output, but inaccessable from any other command (giving file
not found).
I did xfs_check and xfs_repair and as result, now i have no files on my
drive at all (except empty lost+found folder)
Is there anything i can do to get my files back ?
please give more details about kernel, arch, kernel-errors and some output
from xfs_check if possible. do you have any idea what could've caused the
errors? disk problems? power-failure? did you check your memory....
and a well chosen subject line in emails does not hurt either ;-)
--
BOFH excuse #448:
vi needs to be upgraded to vii
|