| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071121210749.GC1299@csclub.uwaterloo.ca> Date: Wed, 21 Nov 2007 16:07:49 -0500 From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) To: alex-lists-linux-kernel@...iev.com Cc: linux-kernel@...r.kernel.org Subject: Re: Identifying a specific affected file on Ext3 on a top of raid0 of raid1s On Wed, Nov 21, 2007 at 03:57:53PM -0500, alex-lists-linux-kernel@...iev.com wrote: > I have a rather nasty situation developing on one of the big 24x7 > production database servers. It seems that a batch of drives in one of the > servers started to fail. > > The file servers are ext3fs on a top of raid-0 over a pair of raid-1 mirrors, > with each of raid-1 mirrors having two drives. The issue is that all four > drives are developing errors. > > Is there a way to determine what files are affected if I know the LBA# of the > errors on individual drives? > > It is running under 2.6.20.x series of kernels. Most likely debugfs can tell you what filesystem block is used by a file and which file is using a given filesystem block, although you would still have to translate the disk block number through the raid layers and partitions to find where it is relative to the begining of the partition the filesystem is on. -- Len Sorensen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists