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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 2 Jun 2008 20:00:38 -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 Tue, Jun 03, 2008 at 12:23:48AM +0200, Christian Kujau wrote:
> On Mon, 2 Jun 2008, Theodore Tso wrote:
>> 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.
>
> Hm, interesting, I did not consider that yet. Thanks for the links, I'll 
> have a look. But again: I don't really care for the data, I was just 
> playing around and wondering why it reported "Device or resource busy"
> when I expected something like "unable to find superblock".

That will only happen if someone else has opened the device with
O_EXCL.  Are you sure you didn't ^Z an e2fsck or some such and then
started a second one, or some such?  

Is this repeatable?

							- 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