RE: ext3 filesystem corruption on md RAID1 device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Hm.. So may be this is not a barrier related.
> >m two smaller Seagate disks to the currently used 1TB disks. There for
> my first thought was a failed disk or memory but they seem to be ok
> based on the SMART and memtest results.
> >
> You may possibly force this to happen sooner like follows:
> find /your-mnt/ -ls > /dev/null #fore fstat for all inodes

The affected filesystem is unfortunately the root filesystem of this server. I have some backups but still would prefer not to force more such errors unless there is no other option. Can I turn on some debugging output or otherwise ensure that if I enforce this error that we get some data that helps diagnose the problem? 
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux