Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_repair\:\s+corrupt\s+inode\s+error\s*$/: 15 ]

Total 15 documents matching your query.

1. xfs_repair: corrupt inode error (score: 1)
Author: Jyrki Muukkonen <jyrki.muukkonen@xxxxxxxxxxx>
Date: Mon, 08 Jan 2007 12:23:32 +0200
Got this error in phase 6 when running xfs_repair 2.8.18 on ~1.2TB partition over the weekend (it took around 60 hours to get to this point :). On earlier versions xfs_repair aborted after ~15-20 hou
/archives/xfs/2007-01/msg00015.html (7,688 bytes)

2. Re: xfs_repair: corrupt inode error (score: 1)
Author:
Date: Mon, 08 Jan 2007 18:07:11 +0200
Some more information: - running 64bit Ubuntu Edgy 2.6.17-10-generic - one processor so xfs_repair was run with two threads - 1.5GB RAM, 3GB swap (at some point the xfs_repair process took a bit over
/archives/xfs/2007-01/msg00027.html (9,011 bytes)

3. RE: xfs_repair: corrupt inode error (score: 1)
Author:
Date: Fri, 12 Jan 2007 12:25:48 +1100
Would it be possible to run xfs_db and print out the inode above: xfs_db <dev> and email the output back? Regards, Barry.
/archives/xfs/2007-01/msg00080.html (10,104 bytes)

4. RE: xfs_repair: corrupt inode error (score: 1)
Author:
Date: Fri, 12 Jan 2007 10:48:12 +0200
OK, here it is: core.magic = 0x494e core.mode = 0102672 core.version = 1 core.format = 3 (btree) core.nlinkv1 = 2308 core.uid = 721387 core.gid = 475570 core.flushiter = 7725 core.atime.sec = Sun Mar
/archives/xfs/2007-01/msg00081.html (11,719 bytes)

5. RE: xfs_repair: corrupt inode error (score: 1)
Author:
Date: Tue, 23 Jan 2007 15:05:05 +0200
Thanks, setting core.mode to 0 on that particular inode helped. -- Jyrki Muukkonen Futurice Oy jyrki.muukkonen@xxxxxxxxxxx +358 41 501 7322
/archives/xfs/2007-01/msg00150.html (14,542 bytes)

6. xfs_repair: corrupt inode error (score: 1)
Author:
Date: Mon, 08 Jan 2007 12:23:32 +0200
Got this error in phase 6 when running xfs_repair 2.8.18 on ~1.2TB partition over the weekend (it took around 60 hours to get to this point :). On earlier versions xfs_repair aborted after ~15-20 hou
/archives/xfs/2007-01/msg00255.html (7,688 bytes)

7. Re: xfs_repair: corrupt inode error (score: 1)
Author: >
Date: Mon, 08 Jan 2007 18:07:11 +0200
Some more information: - running 64bit Ubuntu Edgy 2.6.17-10-generic - one processor so xfs_repair was run with two threads - 1.5GB RAM, 3GB swap (at some point the xfs_repair process took a bit over
/archives/xfs/2007-01/msg00267.html (9,011 bytes)

8. RE: xfs_repair: corrupt inode error (score: 1)
Author: >
Date: Fri, 12 Jan 2007 12:25:48 +1100
Would it be possible to run xfs_db and print out the inode above: xfs_db <dev> and email the output back? Regards, Barry.
/archives/xfs/2007-01/msg00320.html (10,104 bytes)

9. RE: xfs_repair: corrupt inode error (score: 1)
Author: >
Date: Fri, 12 Jan 2007 10:48:12 +0200
OK, here it is: core.magic = 0x494e core.mode = 0102672 core.version = 1 core.format = 3 (btree) core.nlinkv1 = 2308 core.uid = 721387 core.gid = 475570 core.flushiter = 7725 core.atime.sec = Sun Mar
/archives/xfs/2007-01/msg00321.html (11,719 bytes)

10. RE: xfs_repair: corrupt inode error (score: 1)
Author: >
Date: Tue, 23 Jan 2007 15:05:05 +0200
Thanks, setting core.mode to 0 on that particular inode helped. -- Jyrki Muukkonen Futurice Oy jyrki.muukkonen@xxxxxxxxxxx +358 41 501 7322
/archives/xfs/2007-01/msg00390.html (14,542 bytes)

11. xfs_repair: corrupt inode error (score: 1)
Author: Jyrki Muukkonen <jyrki.muukkonen@xxxxxxxxxxx>
Date: Mon, 08 Jan 2007 12:23:32 +0200
Got this error in phase 6 when running xfs_repair 2.8.18 on ~1.2TB partition over the weekend (it took around 60 hours to get to this point :). On earlier versions xfs_repair aborted after ~15-20 hou
/archives/xfs/2007-01/msg00495.html (7,688 bytes)

12. Re: xfs_repair: corrupt inode error (score: 1)
Author: Jyrki Muukkonen <jyrki.muukkonen@xxxxxxxxxxx>
Date: Mon, 08 Jan 2007 18:07:11 +0200
Some more information: - running 64bit Ubuntu Edgy 2.6.17-10-generic - one processor so xfs_repair was run with two threads - 1.5GB RAM, 3GB swap (at some point the xfs_repair process took a bit over
/archives/xfs/2007-01/msg00507.html (9,131 bytes)

13. RE: xfs_repair: corrupt inode error (score: 1)
Author: "Barry Naujok" <bnaujok@xxxxxxxxxxxxxxxxx>
Date: Fri, 12 Jan 2007 12:25:48 +1100
Would it be possible to run xfs_db and print out the inode above: xfs_db <dev> and email the output back? Regards, Barry.
/archives/xfs/2007-01/msg00560.html (10,180 bytes)

14. RE: xfs_repair: corrupt inode error (score: 1)
Author: Jyrki Muukkonen <jyrki.muukkonen@xxxxxxxxxxx>
Date: Fri, 12 Jan 2007 10:48:12 +0200
OK, here it is: core.magic = 0x494e core.mode = 0102672 core.version = 1 core.format = 3 (btree) core.nlinkv1 = 2308 core.uid = 721387 core.gid = 475570 core.flushiter = 7725 core.atime.sec = Sun Mar
/archives/xfs/2007-01/msg00561.html (11,792 bytes)

15. RE: xfs_repair: corrupt inode error (score: 1)
Author: Jyrki Muukkonen <jyrki.muukkonen@xxxxxxxxxxx>
Date: Tue, 23 Jan 2007 15:05:05 +0200
Thanks, setting core.mode to 0 on that particular inode helped. -- Jyrki Muukkonen Futurice Oy jyrki.muukkonen@xxxxxxxxxxx +358 41 501 7322
/archives/xfs/2007-01/msg00630.html (14,686 bytes)

Current List: 1 - 15
Page: [1]

This search system is powered by Namazu