linux-ext4 - Re: e2fsck: Device or resource busy

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Jun 2008 16:21:44 -0400
From:	Theodore Tso <tytso@....edu>
To:	Christian Kujau <lists@...dbynature.de>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: e2fsck: Device or resource busy

On Mon, Jun 02, 2008 at 08:29:24PM +0200, Christian Kujau wrote:
> Hi there,
>
> I'm trying to repair a severely damaged ext4 partition. Actually, I don't 
> care any more for the data, I just wanted to see how far I could get, 
> because the "damage" here is: the partition was 1/3 of a RAID-0 setup :)

The key thing that you need to do when trying to recover from RAID
setups where you are missing one or more disks is to align the pieces
so they are in their original places, with the missing pieces replaced
with a /dev/zero device.

There is a starting point here which you may find helpful:

      http://debian.co.nz/Recovery+of+RAID+and+LVM2.html

      http://tldp.org/HOWTO/LVM-HOWTO/index.html

      http://www.tldp.org/HOWTO/Software-RAID-HOWTO.html 

(I'm assuming here you were using software RAID; if this was a
hardware RAID setup, then you need to know what sort of low-level
format was used by your hardware RAID device.)

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html