* Crush on btrfs device delete missing
@ 2016-08-28 5:22 MASAKI Yuhsuke
2016-08-28 8:06 ` Duncan
0 siblings, 1 reply; 3+ messages in thread
From: MASAKI Yuhsuke @ 2016-08-28 5:22 UTC (permalink / raw)
To: linux-btrfs
btrfs device delete missing always crushes and stop system.
It log console only not STDOUT/STDERR or core file.
This is copy from leaved message on console's last screen.
=====
oops_end+0x9c/0cd0
die+0x4b/0x70
do_trap+0xb2/0x140
do_error_trap+0x89/0x110
? update_inline_extent_backref+0x2ab/0x2b0 [btrfs]
? btrfs_set_lock_blocking_rw+0x80/0c0 [btrfs]
do_invalid_op+0x20/0x30
invalid_op+0x1e/0x30
? update_inline_extent_backref+0x2ab/0x2b0 [btrfs]
? update_inline_extent_backref+0x1e8/0x2b0 [btrfs]
remove_extent_backref+0x3f/0x80 [btrfs]
__btrfs_free_extent.isra.34+0x709/0x80 [btrfs]
__btrfs_run_delayed_refs+0x567/0x1260 [btrfs]
btrfs_run_delayed_refs+0x0x9f/0x2c0 [btrfs]
delayed_ref_async_start+0x94/0xb0 [btrfs]
btrfs_scrubparity_helper+0x77/0x350
btrfs_extent_refs_helper+0xe/0x10 [btrfs]
? process_one_work+0x480/0x480
kthread+0xd8/0xf0
ret_from_fork+0x1f/0x40
? kthread_worker_fn+0x170/0x170
=====
This btrfs volume has seven disks including new blank disk and removed
missing disk, and it's mounted with degraded option.
---
MASAKI Yuhsuke <yek@reasonset.net>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Crush on btrfs device delete missing
2016-08-28 5:22 Crush on btrfs device delete missing MASAKI Yuhsuke
@ 2016-08-28 8:06 ` Duncan
2016-08-28 8:41 ` MASAKI Yuhsuke
0 siblings, 1 reply; 3+ messages in thread
From: Duncan @ 2016-08-28 8:06 UTC (permalink / raw)
To: linux-btrfs
MASAKI Yuhsuke posted on Sun, 28 Aug 2016 14:22:52 +0900 as excerpted:
> btrfs device delete missing always crushes and stop system.
> It log console only not STDOUT/STDERR or core file.
While I'm unlikely to be able to help with the problem, for those who
can, you're missing some critical information, including kernel and btrfs-
progs versions (if they're old, please try a current 4.6 or 4.7 kernel if
on current, or 4.4 if on LTS, and an appropriately matched or newer btrfs
userspace as well), and btrfs filesystem usage or btrfs filesystem show
and btrfs filesystem df outputs.
--
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Crush on btrfs device delete missing
2016-08-28 8:06 ` Duncan
@ 2016-08-28 8:41 ` MASAKI Yuhsuke
0 siblings, 0 replies; 3+ messages in thread
From: MASAKI Yuhsuke @ 2016-08-28 8:41 UTC (permalink / raw)
To: linux-btrfs
Hi Duncan.
Sorry, I was careless.
(And sorry illrelevant To header.)
System is a Kernel 4.7.2 Manjaro Linux default setting.
===
$ uname -r
4.7.2-1-MANJARO
===
and btrfs progs.
===
$ pacman -Q btrfs-progs
btrfs-progs 4.7-1
===
result of btrfs fi usage /path/to/volume
===
Overall:
Device size: 19.10TiB
Device allocated: 10.71TiB
Device unallocated: 8.39TiB
Device missing: 2.73TiB
Used: 10.71TiB
Free (estimated): 4.19TiB (min: 4.19TiB)
Data ratio: 2.00
Metadata ratio: 1.99
Global reserve: 512.00MiB (used: 0.00B)
Data,RAID1: Size:5.34TiB, Used:5.34TiB
/dev/dm-1 1.78TiB
/dev/dm-2 1.78TiB
/dev/dm-3 1.78TiB
/dev/dm-4 1.78TiB
/dev/dm-5 1.78TiB
/dev/mapper/hymaster_6 2.00GiB
missing 1.78TiB
Metadata,single: Size:112.00MiB, Used:0.00B
/dev/dm-1 16.00MiB
/dev/dm-2 16.00MiB
/dev/dm-3 16.00MiB
/dev/dm-4 16.00MiB
/dev/dm-5 24.00MiB
missing 24.00MiB
Metadata,RAID1: Size:14.00GiB, Used:12.40GiB
/dev/dm-1 3.00GiB
/dev/dm-2 3.00GiB
/dev/dm-3 6.00GiB
/dev/dm-4 5.00GiB
/dev/dm-5 5.00GiB
missing 6.00GiB
System,RAID1: Size:32.00MiB, Used:784.00KiB
/dev/dm-1 32.00MiB
/dev/dm-2 32.00MiB
Unallocated:
/dev/dm-1 966.47GiB
/dev/dm-2 965.47GiB
/dev/dm-3 966.50GiB
/dev/dm-4 965.50GiB
/dev/dm-5 965.50GiB
/dev/mapper/hymaster_6 2.73TiB
missing 967.50GiB
===
Result of btrfs filesystem show /path/to/volume
===
Label: 'HyMasterBtr' uuid: c78a98fb-4718-4f30-abae-466ebf6e2d8f
Total devices 7 FS bytes used 5.36TiB
devid 1 size 2.73TiB used 1.79TiB path /dev/mapper/hymaster_1
devid 2 size 2.73TiB used 1.79TiB path /dev/mapper/hymaster_2
devid 4 size 2.73TiB used 1.79TiB path /dev/mapper/hymaster_3
devid 5 size 2.73TiB used 1.79TiB path /dev/mapper/hymaster_4
devid 6 size 2.73TiB used 1.79TiB path /dev/mapper/hymaster_5
devid 7 size 2.73TiB used 2.00GiB path /dev/mapper/hymaster_6
*** Some devices missing
===
Result of btrfs filesystem df
===
Data, RAID1: total=5.34TiB, used=5.34TiB
System, RAID1: total=32.00MiB, used=784.00KiB
Metadata, RAID1: total=14.00GiB, used=12.40GiB
Metadata, single: total=112.00MiB, used=0.00B
GlobalReserve, single: total=512.00MiB, used=0.00B
===
Thank you.
On Sun, 28 Aug 2016 08:06:47 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
> MASAKI Yuhsuke posted on Sun, 28 Aug 2016 14:22:52 +0900 as excerpted:
>
> > btrfs device delete missing always crushes and stop system.
> > It log console only not STDOUT/STDERR or core file.
>
> While I'm unlikely to be able to help with the problem, for those who
> can, you're missing some critical information, including kernel and
> btrfs- progs versions (if they're old, please try a current 4.6 or
> 4.7 kernel if on current, or 4.4 if on LTS, and an appropriately
> matched or newer btrfs userspace as well), and btrfs filesystem usage
> or btrfs filesystem show and btrfs filesystem df outputs.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-08-28 8:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-28 5:22 Crush on btrfs device delete missing MASAKI Yuhsuke
2016-08-28 8:06 ` Duncan
2016-08-28 8:41 ` MASAKI Yuhsuke
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).