| 2007-01-26 19:41:58 |
Tom Metro |
description |
Binary package hint: xfsprogs
(See related bug: "newly created XFS filesystem is corrupt; mount fails".)
Ubuntu Fiesty 2.6.20-5-386; xfsprogs 2.8.18-1
After creating an XFS file system on top of an LVM logical volume:
# mkfs.xfs -b size=4096 -L Videos /dev/video_vg/video_lv -f
meta-data=/dev/video_vg/video_lv isize=256 agcount=32, agsize=4883456 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=156270592, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=4096 blocks=0, rtextents=0
I observed:
# xfs_check /dev/video_vg/video_lv
bad format 0 for inode 130 type 0
bad magic number 0 for inode 144
bad magic number 0 for inode 145
allocated inode 130 has 0 link count
And so ran:
# xfs_repair /dev/video_vg/video_lv
- creating 2 worker thread(s)
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- 14:48:36: scanning filesystem freespace - 32 of 32 allocation
groups done
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- 14:48:36: scanning agi unlinked lists - 32 of 32 allocation
groups done
- process known inodes and perform inode discovery...
[...]
bad magic number 0x0 on inode 130
bad version number 0x0 on inode 130
bad magic number 0x0 on inode 131
bad version number 0x0 on inode 131
[...]
bad magic number 0x0 on inode 130, resetting magic number
bad version number 0x0 on inode 130, resetting version number
bad magic number 0x0 on inode 160, resetting magic number
bad version number 0xfffffff9 on inode 160, resetting version number
[...]
bad magic number 0x0 on inode 177, resetting magic number
bad version number 0x0 on inode 177, resetting version number
- 14:48:36: process known inodes and inode discovery - 64 of 64
inodes done
- process newly discovered inodes...
- 14:48:36: process newly discovered inodes - 32 of 32
allocation groups done
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- 14:48:36: setting up duplicate extent list - 32 of 32
allocation groups done
- check for inodes claiming duplicate blocks...
[...]
- agno = 30
- agno = 31
- 14:48:37: check for inodes claiming duplicate blocks - 64 of
64 inodes done
*** glibc detected *** xfs_repair: double free or corruption (out):
0x081a8e00 ***
(See attachment for full transcript.)
|
Binary package hint: xfsprogs
(See related Bug #81717 : "newly created XFS filesystem is corrupt; mount fails".)
Ubuntu Fiesty 2.6.20-5-386; xfsprogs 2.8.18-1
After creating an XFS file system on top of an LVM logical volume:
# mkfs.xfs -b size=4096 -L Videos /dev/video_vg/video_lv -f
meta-data=/dev/video_vg/video_lv isize=256 agcount=32, agsize=4883456 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=156270592, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=4096 blocks=0, rtextents=0
I observed:
# xfs_check /dev/video_vg/video_lv
bad format 0 for inode 130 type 0
bad magic number 0 for inode 144
bad magic number 0 for inode 145
allocated inode 130 has 0 link count
And so ran:
# xfs_repair /dev/video_vg/video_lv
- creating 2 worker thread(s)
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- 14:48:36: scanning filesystem freespace - 32 of 32 allocation
groups done
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- 14:48:36: scanning agi unlinked lists - 32 of 32 allocation
groups done
- process known inodes and perform inode discovery...
[...]
bad magic number 0x0 on inode 130
bad version number 0x0 on inode 130
bad magic number 0x0 on inode 131
bad version number 0x0 on inode 131
[...]
bad magic number 0x0 on inode 130, resetting magic number
bad version number 0x0 on inode 130, resetting version number
bad magic number 0x0 on inode 160, resetting magic number
bad version number 0xfffffff9 on inode 160, resetting version number
[...]
bad magic number 0x0 on inode 177, resetting magic number
bad version number 0x0 on inode 177, resetting version number
- 14:48:36: process known inodes and inode discovery - 64 of 64
inodes done
- process newly discovered inodes...
- 14:48:36: process newly discovered inodes - 32 of 32
allocation groups done
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- 14:48:36: setting up duplicate extent list - 32 of 32
allocation groups done
- check for inodes claiming duplicate blocks...
[...]
- agno = 30
- agno = 31
- 14:48:37: check for inodes claiming duplicate blocks - 64 of
64 inodes done
*** glibc detected *** xfs_repair: double free or corruption (out):
0x081a8e00 ***
(See attachment for full transcript.)
|
|
| 2008-08-14 13:58:58 |
Hew |
xfsprogs: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance. |
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|
