Bug 116601 - WARN: volumes.c:2376 btrfs_init_new_device+0xcd8/0xed0 RIP: btrfs_show_devname+0x4b/0xd0
Summary: WARN: volumes.c:2376 btrfs_init_new_device+0xcd8/0xed0 RIP: btrfs_show_devnam...
Status: NEW
Alias: None
Product: File System
Classification: Unclassified
Component: btrfs (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Josef Bacik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-18 01:52 UTC by Chris Murphy
Modified: 2016-04-18 02:09 UTC (History)
0 users

See Also:
Kernel Version: 4.5.0-300.fc24.x86_64
Tree: Fedora
Regression: No

Attachments
116601 dmesg (8.54 KB, text/plain)
2016-04-18 01:58 UTC, Chris Murphy 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Chris Murphy 2016-04-18 01:52:26 UTC 
Summary:

Add too small device to existing Btrfs (seed device), which fails, but results in system instability and multiple call traces. It's understood 256K for extra device is too small, maybe that should fail, but at least the kernel probably shouldn't oops.

Steps:

# fallocate -l 2g btrfs.img
# losetup /dev/loop0 btrfs.img
# mkfs.btrfs -dsingle -msingle /dev/loop0
# mount /dev/loop /mnt/0
# cp -a /usr/lib64 /mnt/0
# umount /mnt/0
# btrfstune -S1 /dev/loop0
# mount /dev/loop0 /mnt/0
# modprobe zram
# echo 256K > /sys/block/zram0/disksize
# btrfs dev add /dev/zram0 /mnt/0
Performing full device TRIM (256.00KiB) ...
ERROR: error adding device '/dev/zram0': No space left on device
# umount /mnt/0
**\\ shell hangs
Comment 1 Chris Murphy 2016-04-18 01:58:50 UTC 
Created attachment 213211 [details]
116601 dmesg
Comment 2 Chris Murphy 2016-04-18 02:09:45 UTC 
btrfs-progs-4.5.1-1.fc25.x86_64
Note You need to log in before you can comment on or make changes to this bug.