On Fri, Jan 1, 2016 at 4:47 AM, Rasmus Abrahamsen <btrfs@xxxxxxxxxxx> wrote: > Happy New Year! > > I have a raid with a 1TB, .5TB, 1.5TB and recently added a 4TB and want to remove the 1.5TB. When saying btrfs dev delete it turned into readonly. I am on 4.2.5-1-ARCH and btrfs-progs v4.3.1 what can I do? btrfs fi show lsblk -f btrfs fi usage <pathtomountpointforbtrfsvolumeunderdiscussion> he remove, so I did --since=yesterday > I am looking at the log now, please stnad by. > This is my log > http://pastebin.com/mCPi3y9r What's this? Dec 31 15:03:56 rasmusahome systemd-udevd[6340]: inotify_add_watch(9, /dev/sdd1, 10) failed: No space left on device Dec 31 15:04:01 rasmusahome kernel: sdd: sdd1 Dec 31 15:04:01 rasmusahome systemd-udevd[6341]: inotify_add_watch(9, /dev/sdd1, 10) failed: No space left on device Dec 31 15:05:43 rasmusahome kernel: BTRFS info (device sdb1): disk added /dev/sdd1 Why is udev first complaining about no space left on sdd1, but then it's being added to the btrfs volume? -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
