All of lore.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: cwillu@cwillu.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can't mount removable device if device name changes.
Date: Mon, 12 Apr 2010 09:02:43 +0900	[thread overview]
Message-ID: <4BC26323.3010303@jp.fujitsu.com> (raw)
In-Reply-To: <l2k4853c6511004101849r8c34baebq39774a47bf3c8f19@mail.gmail.com>

Hi,

 What is your kernel version?
 Btrfs hols device names which construct filesystems and
updating device name(device renaming) is merged just in
last month.

Regards,
taruisi

(2010/04/11 10:49), cwillu wrote:
> I've got a btrfs on an sd card, which I'm using as the root fs on a
> beagle.  That's not the problem :)
> 
> The machine I generate my images on has an internal sd reader, and I
> also have a usb card reader.  After creating the fs on the internal
> reader, I ended up plugging it in on the external reader.
> 
> internal: sdd
> external: sdh
> 
> mount /dev/sdh2 /mnt -t btrfs
>> mount: /dev/sdh2: can't read superblock
> [15035.538462] device fsid 48fadf7ed76537-bb9c7266ecb8b2 devid transid
> 8986 /dev/sdh2
> [15035.538462] open /dev/sdd2 failed
> 
> If I plug it back into the internal reader, it mounts fine on /dev/sdd2.
> 
> An strace of btrfsctl -a shows it reading /dev/sdh2, and there's no
> mention of /dev/sdd:
>> open("/dev/sdh2", O_RDONLY)             = 4
>> pread(4, "\2067kF\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2859, 65536) = 2859
> 
> The fs mounts fine on the external reader on a different machine.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
taruisi


      reply	other threads:[~2010-04-12  0:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11  1:49 Can't mount removable device if device name changes cwillu
2010-04-12  0:02 ` TARUISI Hiroaki [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=4BC26323.3010303@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=cwillu@cwillu.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 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.