From: gmack@innerfire.net
To: linux-btrfs@vger.kernel.org
Subject: linux 2.6.34 raid1 btrfs weird mounting issue
Date: Fri, 28 May 2010 14:45:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.1005281439280.26232@mtl.rackplans.net> (raw)
In-Reply-To: <m3hblti0my.fsf@pullcord.laptop.org>
I had my raid set to mount by uuid but that randomly doesn't work so I
changed to mounting by the first partition in the raid.. that worked but
on the next reboot it failed. Changing the mount to the second partition
worked until the next reboot when I needed it to change it back to the
first. Each change seems to last for one reboot.
# mount /dev/sdb1 /home
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
# mount /dev/sdb1 /home
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
mount /dev/sdc1 /home
(worked)
# btrfs-show
failed to read /dev/sr0
Label: none uuid: a2aa44b8-3168-480a-a155-d510e05853e7
Total devices 1 FS bytes used 5.46GB
devid 1 size 29.33GB used 13.29GB path /dev/sda2
Label: fhome uuid: 128ddab5-224d-4f45-abc0-6a07d0f63d47
Total devices 2 FS bytes used 8.24GB
devid 1 size 931.51GB used 21.03GB path /dev/sdb1
devid 2 size 931.51GB used 21.01GB path /dev/sdc1
Gerhard
--
Gerhard Mack
gmack@innerfire.net
<>< As a computer I find your faith in technology amusing.
next prev parent reply other threads:[~2010-05-28 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 19:43 raid1 not reporting the right size gmack
2010-05-27 19:51 ` Chris Ball
2010-05-28 18:45 ` gmack [this message]
2010-05-28 18:52 ` linux 2.6.34 raid1 btrfs weird mounting issue Sebastian 'gonX' Jensen
2010-05-28 19:06 ` Goffredo Baroncelli
2010-05-27 20:04 ` raid1 not reporting the right size Josef Bacik
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=alpine.DEB.1.10.1005281439280.26232@mtl.rackplans.net \
--to=gmack@innerfire.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).