On Sat, Oct 04, 2008 at 09:45:55AM +0200, Martin Bürger wrote: > Hello, > 'space info full' was the only message I got from dmesg. df reports: > space info full doesn't mean the disk is full, just means we've allocated all of the block group chunks that the filesystem can hold, so you will get that message well before you actually run out of disk space. As it stands now btrfs has a short circuit when you hit ~15% free to go ahead an ENOSPC to avoid hitting the many BUG()'s that are sitting around to handle ENOSPC. > /dev/sdb1 33551720 28504548 5047172 > 85% /mnt/btrfstest > > df -i reports: > /dev/sdb1 0 0 0 - /mnt/btrfstest > > Any (e.g., touch, rm) operation on that mounted filesystem lets the > CPU rise and the system hang... > are you running the latest git trees of both btrfs-unstable and btrfs-progs-unstable? I'd expect BUG()'s or something like that, shouldn't be getting hangs. Thanks, Josef -- 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
