From: Theodore Tso <tytso@mit.edu>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck: Device or resource busy
Date: Mon, 2 Jun 2008 20:00:38 -0400 [thread overview]
Message-ID: <20080603000037.GF23119@mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.10.0806030020310.6160@sheep.housecafe.de>
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
prev parent reply other threads:[~2008-06-03 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 18:29 e2fsck: Device or resource busy Christian Kujau
2008-06-02 20:21 ` Theodore Tso
2008-06-02 22:23 ` Christian Kujau
2008-06-03 0:00 ` Theodore Tso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080603000037.GF23119@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.