Hi, I already tried to check the filesystem with last e2fsprogs version (1.41.10) but with this version I did get a segfault. I opened a bug with all the information [1] Thank you! [1] http://sourceforge.net/tracker/?func=detail&aid=2956459&group_id=2406&atid=102406 El dt 23 de 02 de 2010 a les 09:16 -0600, en/na Eric Sandeen va escriure: > Albert Sellarès wrote: > > Hi, > > > > I have the original filesystem (on a logical volume) "intact" because I've > > always worked on snapshots. > > > > The filesystem has less than 2^31 blocks. This system has been correctly > > running for four years and corruption become because of a hardware problem > > with a SAN device. > > > > The output of dumpe2fs -h /dev/storage/cabina is: > > > > dumpe2fs 1.41.9 (22-Aug-2009) > ... > > > Block count: 2077085696 > ... > > > Block size: 4096 > > > Yep, right you are, just figured it was worth a check. > > Since you can safely operate on a snapshot, -maybe- it would be worth > testing with an e2fsprogs which is newer than that which ships with rhel4... > this wouldn't be a RHEL-supported option, but if there is something which > has been fixed upstream it would help identify the problem if > we knew which release fixed it. > > -Eric -- Albert Sellarès GPG id: 0x13053FFE http://www.wekk.net whats@xxxxxxxxxx Linux User: 324456
Attachment:
signature.asc
Description: =?ISO-8859-1?Q?Aix=F2?= =?ISO-8859-1?Q?_=E9s?= una part d'un missatge signada digitalment
_______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
