From: Marco Ceppi <ceppi.marco@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: USB drives going away and causing problems for btrfs
Date: Thu, 7 Jun 2012 20:57:55 -0400 [thread overview]
Message-ID: <CACfbfuUvZHCWiFuiZpBiw1G59W35gttSd9XV4tJhBSAn1_-p-w@mail.gmail.com> (raw)
I have three hard-drives attached to a media pc via USB (yes, this is
far from idea and I'm procuring the hardware to resolve this). As USB
seems to be crap in general (or something is not working) the drives
get dropped from time to time. In past times this hasn't been an
issue. I was able to force umount the stale mount point and re-mount
with the new device names (/dev/sdb, /dev/sdc, /deb/sdd being
re-written to /dev/sdd, sde, sdf). However, this evening when this
happened the drives wouldn't come back up. After speaking with
darkwing in the the #btrfs room it looks as though the metadata is
corrupt. I've gathered all the logs I could of the incident and
aftermath in hopes that it will help lead developers to better error
handling when poor fools, such as myself, attach large drives via USB.
Kernel log of the dropping incident: http://paste.ubuntu.com/1029622/
btrfsck: http://paste.ubuntu.com/1029589/
btrfs-debug-tree after a reboot: http://paste.ubuntu.com/1029635/
btrfs fi show: http://paste.ubuntu.com/1029638/
Linux media-pc 3.4.0-4-generic #9~precise1-Ubuntu SMP Tue Jun 5
01:25:26 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
btrfs-tools 0.19+20120421-0daily6~bzr457~precise1
Running btrfsck with the --super options and --repair yielded the same
results. If there are any additional logs I could provide or questions
i could answer let me know.
Thanks,
Marco Ceppi
reply other threads:[~2012-06-08 0:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACfbfuUvZHCWiFuiZpBiw1G59W35gttSd9XV4tJhBSAn1_-p-w@mail.gmail.com \
--to=ceppi.marco@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).