On Wed, 15 Jan 2014 21:22:08 +0100
Tomasz Chmielewski man...@wpkg.org wrote:
What kernel version? Can you:
umount
dmesg -n7
mount
And then try to reproduce the behavior and note any kernel messages
in dmesg?
Turns out it's reproducible, with 3.13-rc8.
After reboot, I've
I'm no longer able to write to this btrfs filesystem:
# df -h /home
Filesystem Size Used Avail Use% Mounted on
/dev/sdb4 5.2T 3.6T 1.6T 71% /home
# btrfs fi show /home
Label: crawler-btrfs uuid: 60f1759c-45f6-4484-9f60-66a4e9bbf2b6
Total devices 2 FS bytes used 1.80TiB
Tomasz Chmielewski posted on Wed, 15 Jan 2014 11:55:43 +0100 as excerpted:
I'm no longer able to write to this btrfs filesystem:
# df -h /home
Filesystem Size Used Avail Use% Mounted on
/dev/sdb4 5.2T 3.6T 1.6T 71% /home
FWIW, standard df doesn't really know how to work with
On Jan 15, 2014, at 3:55 AM, Tomasz Chmielewski man...@wpkg.org wrote:
I'm no longer able to write to this btrfs filesystem:
# df -h /home
Filesystem Size Used Avail Use% Mounted on
/dev/sdb4 5.2T 3.6T 1.6T 71% /home
# btrfs fi show /home
Label: crawler-btrfs uuid:
Am Mittwoch, 15. Januar 2014, 19:05:41 schrieb Duncan:
But just as my already allocated mixed-mode chunks were just about full
and I needed another one allocated to complete the job, so your data
chunks are full or very close, according to btrfs fi df, and you need a
new one allocated (and
# dd if=/dev/urandom of=bigfile
dd: writing to `bigfile': No space left on device
186+0 records in
185+0 records out
94720 bytes (95 kB) copied, 0.0144045 s, 6.6 MB/s
I don't understand why - can anyone explain?
What kernel version? Can you:
umount
dmesg -n7
mount
And
Martin Steigerwald posted on Wed, 15 Jan 2014 20:40:29 +0100 as excerpted:
Am Mittwoch, 15. Januar 2014, 19:05:41 schrieb Duncan:
But just as my already allocated mixed-mode chunks were just about full
and I needed another one allocated to complete the job, so your data
chunks are full or
