From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS not mountable, recover won't work
Date: Mon, 10 Apr 2017 02:38:59 +0000 (UTC) [thread overview]
Message-ID: <pan$7c27b$c263c2d$90d3ff1f$9c677070@cox.net> (raw)
In-Reply-To: CAJCQCtRqidKACy7SAEzpEGLK1PbWQZgbesaLhLEVntMPz9aG5g@mail.gmail.com
Chris Murphy posted on Sun, 09 Apr 2017 15:25:18 -0600 as excerpted:
> On Sun, Apr 9, 2017 at 11:17 AM, Malte Eggers
> <m.eggers@campus.tu-berlin.de> wrote:
>> Hi,
>>
>> After suspending and waking up my laptop with the external hard drive
>> connected, I could no longer access the files on it. So I unmounted and
>> remounted it, only to discover that I could no longer mount it.
This is the only message from the thread I'm seeing ATM, so I'll reply
here. Agreed with C Murphy on the btrfs stuff, but my reply is on a
different tangent.
If your external hard drive is USB (not ESATA or other non-USB, couldn't
tell from the context CM quoted, which may or may not have been the
entire post), you are likely running into a known issue... with an
available solution. =:^)
FWIW I found out about this when I had a laptop with two USB-connected
CompactFlash slots, one of which was designed for effectively permanent
installation (the CF didn't stick out when inserted), the other for
temporary use (it stuck out and was thus easier to remove, but also easy
to damage either it or the slot if it was left inserted during
transport). But the permanent one wouldn't stay mounted over suspend...
until I found out about this and changed the kernel option. Looks like
you might be hitting the same issue.
The official Linux kernel documentation describing the problem and
optional solution is:
$KERNEL_DIR/Documentation/usb/persist.txt
Read that first. But that only explains the problem and gives you a way
to deal with it on a per-USB-device basis by writing to the appropriate
sysfs file. There's also a kernel option that lets you change the
default:
CONFIG_USB_DEFAULT_PERSIST
In the kernel config that's found under:
Device Drivers
USB support
Support for Host-side USB
Enable USB persist by default
If you use a distro-built kernel, you may want to at least check whether
they enabled that option or not.
If you build your own kernel, you may of course set that option as you
wish. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-04-10 2:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 17:17 BTRFS not mountable, recover won't work Malte Eggers
2017-04-09 21:25 ` Chris Murphy
2017-04-10 2:38 ` Duncan [this message]
2017-04-10 7:55 ` Malte Eggers
2017-04-10 8:18 ` Qu Wenruo
2017-04-10 8:37 ` Malte Eggers
2017-04-10 8:53 ` Qu Wenruo
2017-04-10 10:40 ` Malte Eggers
2017-04-13 11:45 ` Malte Eggers
2017-04-14 0:40 ` Qu Wenruo
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='pan$7c27b$c263c2d$90d3ff1f$9c677070@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).