From: Anand Jain <Anand.Jain@oracle.com>
To: Saran Neti <sarannmr@gmail.com>, linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: Re: Unable to rebuild a 3 drive raid1 - blocked for more than 120 seconds.
Date: Fri, 02 May 2014 10:16:51 +0800 [thread overview]
Message-ID: <53630013.8030803@oracle.com> (raw)
In-Reply-To: <CAE6A3M0zmzDmLKzRDALNeLsqx72ttC8CA74-GfuSXN1TwJW-0A@mail.gmail.com>
> I had 3 x 3 TB drives in an almost full btrfs raid1 setup containing
> only large (~20 GB) files linearly written and not modified after.
> Then one of the drives got busted.
> Mounting the fs in degraded mode
> and adding a new fresh drive to rebuild raid1, generated several
> "...blocked for more than 120 seconds." messages. I left it running
> for a couple of days, but "btrfs device add..." command wouldn't
> return. I did a hard reboot, and after a degraded mount, am unable to
> unmount, or add a drive or delete missing without getting stuck with
> the same error. iostat shows no disk activity. When attempting an
> unmount, both "umount" and "[btrfs-transacti]" processes become
> defunct. Tried -o skip_balance as well to no avail.
> # btrfs fi show
> Label: 'cohenraid1' uuid: 288723c3-2e98-4a6c-87d3-058451d87d26
> Total devices 3 FS bytes used 3.44TiB
> devid 1 size 2.73TiB used 2.19TiB path /dev/sdg1
> devid 2 size 2.73TiB used 2.46TiB path /dev/sdf1
> *** Some devices missing
the below patch would add ambiguity in the situation like this,
We would not know a critical info - whether the btrfs kernel
knows about the missing device...
http://marc.info/?l=linux-btrfs&m=139175679431525&w=2
prev parent reply other threads:[~2014-05-02 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 4:48 Unable to rebuild a 3 drive raid1 - blocked for more than 120 seconds Saran Neti
2014-05-01 6:01 ` Duncan
2014-05-02 1:58 ` Chris Murphy
2014-05-02 2:23 ` Chris Murphy
2014-05-02 4:13 ` Chris Murphy
2014-05-02 2:16 ` Anand Jain [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=53630013.8030803@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sarannmr@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).