* mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda"
@ 2010-01-24 5:53 0bo0
2010-01-24 8:02 ` Goffredo Baroncelli
0 siblings, 1 reply; 10+ messages in thread
From: 0bo0 @ 2010-01-24 5:53 UTC (permalink / raw)
To: linux-btrfs
after a simple reboot,
btrfs-show
Label: TEST uuid: 2ac85206-2d88-47d7-a1e7-a93d80b199f8
Total devices 4 FS bytes used 28.00KB
devid 1 size 931.51GB used 2.03GB path /dev/sda
devid 2 size 931.51GB used 2.01GB path /dev/sdb
devid 3 size 931.51GB used 2.01GB path /dev/sdc
devid 4 size 931.51GB used 2.01GB path /dev/sdd
but,
mount /dev/sda /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
where,
tail -f /var/log/messages,
Jan 23 21:49:23 test kernel: [ 94.949335] device fsid
f9452f77524a701a-28bb2c0e9bab5a99 devid 1 transid 17 /dev/sda
Jan 23 21:49:23 test kernel: [ 94.951716] btrfs: failed to read
the system array on sda
Jan 23 21:49:23 test kernel: [ 94.952748] btrfs: open_ctree failed
mkfs.btrfs -m raid10 -d raid10 /dev/sd[abcd]
WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
adding device /dev/sdb id 2
adding device /dev/sdc id 3
adding device /dev/sdd id 4
fs created label (null) on /dev/sda
nodesize 4096 leafsize 4096 sectorsize 4096 size 3.64TB
Btrfs Btrfs v0.19
mount /dev/sda /mnt
df -H | grep -i sda
/dev/sda 4.1T 29k 4.1T 1% /mnt
fyi,
lsb_release -ri
Distributor ID: SUSE LINUX
Release: 11.2
uname -a
Linux test 2.6.31.8-0.1-xen #1 SMP 2009-12-15 23:55:40 +0100 x86_64
x86_64 x86_64 GNU/Linux
rpm -qa | grep btr
btrfsprogs-0.19-10.1.x86_64
a bug?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda"
2010-01-24 5:53 mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda" 0bo0
@ 2010-01-24 8:02 ` Goffredo Baroncelli
2010-01-24 11:53 ` "*** Some devices missing ***" & "Unable to stat /dev/sdg" error messages Ronald Kasl
2010-01-24 16:46 ` mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda" 0bo0
0 siblings, 2 replies; 10+ messages in thread
From: Goffredo Baroncelli @ 2010-01-24 8:02 UTC (permalink / raw)
To: 0bo0; +Cc: linux-btrfs
On Sunday 24 January 2010, 0bo0 wrote:
> after a simple reboot,
^^^^^^
Have you do
# btrfsctl -a
before mounting the filesystem ? This command scans all the block devices
searching the btrfs volume. So when you mount a device of an array the system
is able to retrieves the others.
[..]
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
^ permalink raw reply [flat|nested] 10+ messages in thread
* "*** Some devices missing ***" & "Unable to stat /dev/sdg" error messages
2010-01-24 8:02 ` Goffredo Baroncelli
@ 2010-01-24 11:53 ` Ronald Kasl
2010-01-24 13:23 ` Goffredo Baroncelli
2010-01-24 16:46 ` mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda" 0bo0
1 sibling, 1 reply; 10+ messages in thread
From: Ronald Kasl @ 2010-01-24 11:53 UTC (permalink / raw)
Cc: linux-btrfs
Hello, .. what do I do when I get " *** Some devices missing " and " "Unable to stat /dev/sdg" , error message after drive is hotswaped or die ?
this is what I did?
1. mkfs.btrfs -m raid1 -d raid10 -L btrfs_label_01 /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sdf /dev/sdg
2. mount -t btrfs -o compress /dev/sda /mnt/btrfs
3. figgle around testing the system , then I tremoved one of the disk (/dev/sdg) to see what happen, which is when I get the "device missing" message in the btrfs-show that is understandable, but I cannot bring the disk back after it's "live" again .... the FS worked just fine without the disk, I just don't know how to bring it back to the btrfs pool of disks
# btrfs-show
failed to read /dev/sdg1
failed to read /dev/sdg
failed to read /dev/sr0
Label: btrfs_label_01 uuid: 0135dae3-61d8-430e-80ba-3e254d404371
Total devices 6 FS bytes used 28.00KB
devid 1 size 931.51GB used 1.02GB path /dev/sda
devid 2 size 931.51GB used 1.00GB path /dev/sdb
devid 3 size 931.51GB used 2.00GB path /dev/sdc
devid 4 size 931.51GB used 2.00GB path /dev/sdd
devid 5 size 931.48GB used 1.01GB path /dev/sdf
*** Some devices missing
4. I tried what is on the wiki under "replacing failed devices, but I
was getting nowhere since I'm getting "Unable to stat /dev/sdg" error
message when I'm trying to remove the failed device.
this is what I did
umount /mnt/btrfs
mount -o degraded /dev/sda /mnt/btrfs
btrfs-vol -r /dev/sdg /mnt/btrfs
.. then I get the "Unable to stat /dev/sdg" message
5. I hotswap the disk back to its bay, but the drive still did not show up .. it just keept "missing" until I reboot the system, then I could mount it ... yet after the reboot I had those "
mount: wrong fs type, bad option, bad superblock on /dev/sda ..." error messages untill I did something and then it work (I guess I had to run the btrfsctl -a command that showed all the disk present)
any idea what to do to bring hotswaped drive back to to system? thanks!!
btw. do I need to create a partition with fdisk to use the disks with btrfs -- first I just used the new disk without creating partition on them, but then I read some howto and there was stated that one needs to create a partition first --- I tried that and I had the same problem described above and it seems that btrfs doesn't care
thanks!!!
http://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
Goffredo Baroncelli wrote:
> On Sunday 24 January 2010, 0bo0 wrote:
>
>> after a simple reboot,
>>
> ^^^^^^
> Have you do
>
> # btrfsctl -a
>
> before mounting the filesystem ? This command scans all the block devices
> searching the btrfs volume. So when you mount a device of an array the system
> is able to retrieves the others.
>
> [..]
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: "*** Some devices missing ***" & "Unable to stat /dev/sdg" error messages
2010-01-24 11:53 ` "*** Some devices missing ***" & "Unable to stat /dev/sdg" error messages Ronald Kasl
@ 2010-01-24 13:23 ` Goffredo Baroncelli
2010-01-24 16:36 ` kernel BUG at /build/buildd/linux-2.6.32/fs/btrfs/volumes.c:1772! RK
0 siblings, 1 reply; 10+ messages in thread
From: Goffredo Baroncelli @ 2010-01-24 13:23 UTC (permalink / raw)
To: linux-btrfs
On Sunday 24 January 2010, Ronald Kasl wrote:
> Hello, .. what do I do when I get " *** Some devices missing " and " "Unable
to stat /dev/sdg" , error message after drive is hotswaped or die ?
>
> this is what I did?
> 1. mkfs.btrfs -m raid1 -d raid10 -L btrfs_label_01 /dev/sda /dev/sdb
/dev/sdc /dev/sdd /dev/sdf /dev/sdg
> 2. mount -t btrfs -o compress /dev/sda /mnt/btrfs
> 3. figgle around testing the system , then I tremoved one of the disk
(/dev/sdg) to see what happen, which is when I get the "device missing"
message in the btrfs-show that is understandable, but I cannot bring the disk
back after it's "live" again .... the FS worked just fine without the disk, I
just don't know how to bring it back to the btrfs pool of disks
>
> # btrfs-show
> failed to read /dev/sdg1
> failed to read /dev/sdg
> failed to read /dev/sr0
> Label: btrfs_label_01 uuid: 0135dae3-61d8-430e-80ba-3e254d404371
> Total devices 6 FS bytes used 28.00KB
> devid 1 size 931.51GB used 1.02GB path /dev/sda
> devid 2 size 931.51GB used 1.00GB path /dev/sdb
> devid 3 size 931.51GB used 2.00GB path /dev/sdc
> devid 4 size 931.51GB used 2.00GB path /dev/sdd
> devid 5 size 931.48GB used 1.01GB path /dev/sdf
>
> *** Some devices missing
>
> 4. I tried what is on the wiki under "replacing failed devices, but I
> was getting nowhere since I'm getting "Unable to stat /dev/sdg" error
> message when I'm trying to remove the failed device.
>
> this is what I did
> umount /mnt/btrfs
> mount -o degraded /dev/sda /mnt/btrfs
> btrfs-vol -r /dev/sdg /mnt/btrfs
^^^^^^^^
> . then I get the "Unable to stat /dev/sdg" message
It should be (see
http://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
"Replacing Failed Devices")
# btrfs-vol -r missing /mnt/btrfs
But on my machine raised a segmentation fault.
BR
Goffredo
> 5. I hotswap the disk back to its bay, but the drive still did not show up
.. it just keept "missing" until I reboot the system, then I could mount it
... yet after the reboot I had those "
> mount: wrong fs type, bad option, bad superblock on /dev/sda ..." error
messages untill I did something and then it work (I guess I had to run the
btrfsctl -a command that showed all the disk present)
>
> any idea what to do to bring hotswaped drive back to to system? thanks!!
>
> btw. do I need to create a partition with fdisk to use the disks with btrfs
-- first I just used the new disk without creating partition on them, but then
I read some howto and there was stated that one needs to create a partition
first --- I tried that and I had the same problem described above and it seems
that btrfs doesn't care
>
> thanks!!!
>
>
>
> http://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
>
> Goffredo Baroncelli wrote:
> > On Sunday 24 January 2010, 0bo0 wrote:
> >
> >> after a simple reboot,
> >>
> > ^^^^^^
> > Have you do
> >
> > # btrfsctl -a
> >
> > before mounting the filesystem ? This command scans all the block devices
> > searching the btrfs volume. So when you mount a device of an array the
system
> > is able to retrieves the others.
> >
> > [..]
> >
> >
>
> --
> 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
>
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
^ permalink raw reply [flat|nested] 10+ messages in thread
* kernel BUG at /build/buildd/linux-2.6.32/fs/btrfs/volumes.c:1772!
2010-01-24 13:23 ` Goffredo Baroncelli
@ 2010-01-24 16:36 ` RK
0 siblings, 0 replies; 10+ messages in thread
From: RK @ 2010-01-24 16:36 UTC (permalink / raw)
Cc: linux-btrfs
.. btrfs-vol -r missing /mnt/btrfs will end with segmentation fault due to this kernel BUG
(this box runs ubuntu server 10.02 Alpha 2 and the btrfs-tools package is from the ubuntu depository)
# btrfs-show
failed to read /dev/sdf
failed to read /dev/sr0
Label: btrfs_label_01 uuid: acc4b180-4a26-43cf-a103-1fc83faced1a
Total devices 6 FS bytes used 2.00GB
devid 1 size 931.51GB used 1.02GB path /dev/sda
devid 2 size 931.51GB used 1.00GB path /dev/sdb
devid 3 size 931.51GB used 2.00GB path /dev/sdc
devid 4 size 931.51GB used 2.00GB path /dev/sdd
devid 6 size 931.48GB used 1.01GB path /dev/sdg
*** Some devices missing
Btrfs Btrfs v0.19
# umount /mnt/btrfs
# btrfsctl -a
Scanning for Btrfs filesystems
failed to read /dev/sdg
failed to read /dev/sr0
# mount -o degraded /dev/sda /mnt/btrfs
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sde1 66G 3.8G 59G 7% /
/dev/sda 5.5T 28K 5.5T 1% /mnt/btrfs
# btrfs-vol -r missing /mnt/btrfs
removing missing devices from /mnt/btrfs
Segmentation fault
# dmsg
**
[ 482.623701] ------------[ cut here ]------------
[ 482.623703] kernel BUG at /build/buildd/linux-2.6.32/fs/btrfs/volumes.c:1772!
[ 482.623706] invalid opcode: 0000 [#1] SMP
[ 482.623709] last sysfs file:
/sys/devices/pci0000:00/0000:00:06.0/0000:02:05.0/host1/target1:0:0/1:0:0:0/block/sdb/uevent
[ 482.623712] CPU 0
[ 482.623714] Modules linked in: btrfs zlib_deflate crc32c libcrc32c
aoe binfmt_misc snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss
snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi
snd_seq_midi_event snd_seq snd_timer snd_seq_device snd ppdev parport_pc
soundcore snd_page_alloc amd64_edac_mod i2c_amd756 amd_rng psmouse
serio_raw i2c_amd8111 edac_core k8temp edac_mce_amd shpchp lp parport
fbcon tileblit font bitblit softcursor vga16fb vgastate r8169 ohci1394
mii aic7xxx ieee1394 e1000 scsi_transport_spi aacraid radeon ttm floppy
drm_kms_helper drm i2c_algo_bit
[ 482.623754] Pid: 3417, comm: btrfs-vol Not tainted 2.6.32-11-server
#15-Ubuntu To Be Filled By O.E.M.
[ 482.623757] RIP: 0010:[<ffffffffa03671d4>] [<ffffffffa03671d4>]
btrfs_relocate_chunk+0x2f4/0x320 [btrfs]
[ 482.623788] RSP: 0018:ffff8800baaf7c88 EFLAGS: 00010286
[ 482.623790] RAX: 00000000ffffffe4 RBX: ffff8800a7c77100 RCX:
ffff8800bc35d000
[ 482.623792] RDX: 0000000000000000 RSI: ffffea000292bc58 RDI:
0000000000000206
[ 482.623795] RBP: ffff8800baaf7d18 R08: 0000000000000036 R09:
000000000000c101
[ 482.623797] R10: 0000000000000005 R11: 0000000000000000 R12:
ffff8800bc3b4000
[ 482.623799] R13: 0000000000000020 R14: 0000000000000000 R15:
0000000000000003
[ 482.623802] FS: 00007f306b2ac740(0000) GS:ffff880001c00000(0000)
knlGS:0000000000000000
[ 482.623804] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 482.623806] CR2: 00007f306ac16ac0 CR3: 00000000aa012000 CR4:
00000000000006f0
[ 482.623808] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 482.623810] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 482.623813] Process btrfs-vol (pid: 3417, threadinfo
ffff8800baaf6000, task ffff8800a7c68000)
[ 482.623815] Stack:
[ 482.623816] 0000000000000da0 ffff8800aa275c00 ffff8800baaf7d18
ffffffffa03537a5
[ 482.623820] <0> ffff8800baaf7cd8 ffff8800ba7c80e8 0000000000000100
ffff8800ba7c80f0
[ 482.623823] <0> ffff8800a7d45000 ffff8800a3c3c108 ffff8800a7d43000
0000000041c00000
[ 482.623827] Call Trace:
[ 482.623839] [<ffffffffa03537a5>] ?
btrfs_dev_extent_chunk_offset+0xe5/0xf0 [btrfs]
[ 482.623848] [<ffffffffa0367701>] btrfs_shrink_device+0x221/0x390 [btrfs]
[ 482.623857] [<ffffffffa0367cd1>] btrfs_rm_device+0x1e1/0x480 [btrfs]
[ 482.623865] [<ffffffffa036dd97>] btrfs_ioctl+0x1c7/0x3f0 [btrfs]
[ 482.623871] [<ffffffff811508d2>] vfs_ioctl+0x22/0xa0
[ 482.623876] [<ffffffff812b1fba>] ? __up_read+0x9a/0xc0
[ 482.623879] [<ffffffff81150a71>] do_vfs_ioctl+0x81/0x410
[ 482.623884] [<ffffffff8108780e>] ? up_read+0xe/0x10
[ 482.623889] [<ffffffff815642cf>] ? do_page_fault+0x18f/0x360
[ 482.623891] [<ffffffff81150e81>] sys_ioctl+0x81/0xa0
[ 482.623897] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b
[ 482.623898] Code: 48 8b 7d c0 e8 be d2 ff ff 48 8b 75 c0 4c 89 e7 e8
42 ad fd ff 48 83 c4 68 31 c0 5b 41 5c 41 5d 41 5e 41 5f c9 c3 90 0f 0b
eb fe <0f> 0b eb fe 0f 0b eb fe 0f 0b eb fe 0f 0b eb fe 0f 0b eb fe 0f
[ 482.623924] RIP [<ffffffffa03671d4>]
btrfs_relocate_chunk+0x2f4/0x320 [btrfs]
[ 482.623933] RSP <ffff8800baaf7c88>
[ 482.623936] ---[ end trace 92bb2e88797fdf58 ]---
#
***
# lsscsi -g
[0:0:0:0] disk ATA ST31000520AS CC32 /dev/sda /dev/sg0
[1:0:0:0] disk ATA ST31000520AS CC32 /dev/sdb /dev/sg1
[2:0:0:0] disk ATA ST31000520AS CC32 /dev/sdc /dev/sg2
[3:0:0:0] disk ATA ST31000520AS CC32 /dev/sdd /dev/sg3
[4:0:0:0] cd/dvd SONY CD-RW CRX320E NYK5 /dev/sr0 /dev/sg4
[6:0:0:0] disk Adaptec system V1.0 /dev/sde /dev/sg5
[6:0:1:0] disk Adaptec disk2 V1.0 /dev/sdf /dev/sg6
[6:0:2:0] disk Adaptec disk3 V1.0 /dev/sdg /dev/sg7
[6:1:0:0] disk WDC WD740GD-00FLA2 31.0 - /dev/sg8
[6:1:1:0] disk WDC WD740GD-00FLA2 31.0 - /dev/sg9
[6:1:2:0] disk ST310005 20AS CC32 - /dev/sg10
[6:1:3:0] disk ST310005 20AS CC32 - /dev/sg11
**
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda"
2010-01-24 8:02 ` Goffredo Baroncelli
2010-01-24 11:53 ` "*** Some devices missing ***" & "Unable to stat /dev/sdg" error messages Ronald Kasl
@ 2010-01-24 16:46 ` 0bo0
2010-01-24 23:35 ` Leszek Ciesielski
1 sibling, 1 reply; 10+ messages in thread
From: 0bo0 @ 2010-01-24 16:46 UTC (permalink / raw)
To: Goffredo Baroncelli; +Cc: linux-btrfs
hi
On Sun, Jan 24, 2010 at 12:02 AM, Goffredo Baroncelli
<kreijack@gmail.com> wrote:
> On Sunday 24 January 2010, 0bo0 wrote:
>> after a simple reboot,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^^^^^^
> Have you do
>
> =A0# btrfsctl -a
>
> before mounting the filesystem ? This command scans all the block dev=
ices
> searching the btrfs volume. So when you mount a device of an array th=
e system
> is able to retrieves the others.
that does the trick! and, i found/understood the reference in tthe
wiki. thanks.
how would that, then, get handled for automount @ boot via fstab? i
guess that the scan needs to get done as well ...
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda"
2010-01-24 16:46 ` mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda" 0bo0
@ 2010-01-24 23:35 ` Leszek Ciesielski
2010-01-25 5:00 ` 0bo0
0 siblings, 1 reply; 10+ messages in thread
From: Leszek Ciesielski @ 2010-01-24 23:35 UTC (permalink / raw)
To: 0bo0; +Cc: Goffredo Baroncelli, linux-btrfs
On Sun, Jan 24, 2010 at 5:46 PM, 0bo0 <0.bugs.only.0@gmail.com> wrote:
> hi
>
> On Sun, Jan 24, 2010 at 12:02 AM, Goffredo Baroncelli
> <kreijack@gmail.com> wrote:
>> On Sunday 24 January 2010, 0bo0 wrote:
>>> after a simple reboot,
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ^^^^^^
>> Have you do
>>
>> =A0# btrfsctl -a
>>
>> before mounting the filesystem ? This command scans all the block de=
vices
>> searching the btrfs volume. So when you mount a device of an array t=
he system
>> is able to retrieves the others.
>
> that does the trick! =A0and, i found/understood the reference in tthe
> wiki. thanks.
>
> how would that, then, get handled for automount @ boot via fstab? =A0=
i
> guess that the scan needs to get done as well ...
> --
Please see this discussion:
http://thread.gmane.org/gmane.comp.file-systems.btrfs/4126/focus=3D4187
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda"
2010-01-24 23:35 ` Leszek Ciesielski
@ 2010-01-25 5:00 ` 0bo0
2010-01-25 18:19 ` Goffredo Baroncelli
0 siblings, 1 reply; 10+ messages in thread
From: 0bo0 @ 2010-01-25 5:00 UTC (permalink / raw)
To: Leszek Ciesielski; +Cc: Goffredo Baroncelli, linux-btrfs
On Sun, Jan 24, 2010 at 3:35 PM, Leszek Ciesielski <skolima@gmail.com> =
wrote:
>> how would that, then, get handled for automount @ boot via fstab? =A0=
i
>> guess that the scan needs to get done as well ...
>> --
>
> Please see this discussion:
> http://thread.gmane.org/gmane.comp.file-systems.btrfs/4126/focus=3D41=
87
Thanks for the reference.
@ that link,
"Would this option ["mount -t btrfs -o device=3D/dev/sdb2 /dev/sda2
/mnt"] work on boot, bypasing the need for "btrfsctl -a" to mount a
multi-device filesystem?"
would translate how, in my case, to an fstab entry?
/dev/sda /mnt btrfs
device=3D/dev/sdb,device=3D/dev/sdc,device=3D/dev/sdd 1 2
?
thanks
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda"
2010-01-25 5:00 ` 0bo0
@ 2010-01-25 18:19 ` Goffredo Baroncelli
2010-01-25 19:33 ` 0bo0
0 siblings, 1 reply; 10+ messages in thread
From: Goffredo Baroncelli @ 2010-01-25 18:19 UTC (permalink / raw)
To: 0bo0; +Cc: linux-btrfs, Leszek Ciesielski
On Monday 25 January 2010, 0bo0 wrote:
> On Sun, Jan 24, 2010 at 3:35 PM, Leszek Ciesielski <skolima@gmail.com>
wrote:
> >> how would that, then, get handled for automount @ boot via fstab? i
> >> guess that the scan needs to get done as well ...
> >> --
> >
> > Please see this discussion:
> > http://thread.gmane.org/gmane.comp.file-systems.btrfs/4126/focus=4187
>
> Thanks for the reference.
>
> @ that link,
>
> "Would this option ["mount -t btrfs -o device=/dev/sdb2 /dev/sda2
> /mnt"] work on boot, bypasing the need for "btrfsctl -a" to mount a
> multi-device filesystem?"
>
>
> would translate how, in my case, to an fstab entry?
>
> /dev/sda /mnt btrfs
> device=/dev/sdb,device=/dev/sdc,device=/dev/sdd 1 2
>
> ?
Yes; it works for me.
> thanks
> --
> 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
>
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda"
2010-01-25 18:19 ` Goffredo Baroncelli
@ 2010-01-25 19:33 ` 0bo0
0 siblings, 0 replies; 10+ messages in thread
From: 0bo0 @ 2010-01-25 19:33 UTC (permalink / raw)
To: Goffredo Baroncelli; +Cc: linux-btrfs, Leszek Ciesielski
On Mon, Jan 25, 2010 at 10:19 AM, Goffredo Baroncelli
<kreijack@gmail.com> wrote:
>> =A0 =A0/dev/sda =A0 =A0/mnt =A0 =A0btrfs device=3D/dev/sdb,device=3D=
/dev/sdc,device=3D/dev/sdd =A0 =A0 1 2
>
> Yes; it works for me.
thanks for the confirmation.
verifying, with that in /etc/fstab, after boot i see,
mount | grep sda
/dev/sda on /mnt type btrfs
(rw,device=3D/dev/sdb,device=3D/dev/sdc,device=3D/dev/sdd)
which apparenlty worked.
still, the RAID size is wrong ...
df -H | grep sda
/dev/sda 4.1T 29k 4.1T 1% /mnt
but that's a different thread.
thanks again.
--
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
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2010-01-25 19:33 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-24 5:53 mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda" 0bo0
2010-01-24 8:02 ` Goffredo Baroncelli
2010-01-24 11:53 ` "*** Some devices missing ***" & "Unable to stat /dev/sdg" error messages Ronald Kasl
2010-01-24 13:23 ` Goffredo Baroncelli
2010-01-24 16:36 ` kernel BUG at /build/buildd/linux-2.6.32/fs/btrfs/volumes.c:1772! RK
2010-01-24 16:46 ` mount after reboot of btrfs RAID-10 fails with "btrfs: failed to read the system array on sda" 0bo0
2010-01-24 23:35 ` Leszek Ciesielski
2010-01-25 5:00 ` 0bo0
2010-01-25 18:19 ` Goffredo Baroncelli
2010-01-25 19:33 ` 0bo0
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).