On Wed, Jul 17, 2013 at 6:04 PM, Josef Bacik <[email protected]> wrote: > On Wed, Jul 17, 2013 at 05:44:23PM -0500, Jon Nelson wrote: >> I had a btrfs filesystem under 3.9.8 that failed /hard/ today. So hard >> that the filesystem could not be mounted because there wasn't enough >> free space, unless it was mounted read only. >> >> This happened after I ran out of metadata space (is there a way to >> increase the amount of metadata storage) while still having many gigs >> free of data space, as reported by btrfs fi df. I tried balancing the >> metadata, defrag'ing files (with -czlib) and even tried mounting with >> -o remount,metadata_ratio={several values}, none of which worked, and >> then it crashed hard. >> >> First, it killed systemd's logger (journald), which refused to >> start.Following the crash, I was not able to mount the filesystem >> without -o ro. -o recovery did not work. >> > > Can you try btrfs-next, I did some work in this area in the last few months.
Unfortunately, I could not wait. I reaaaaly needed that system back up, so I copied everything off, reformatted with ext4, and copied it all back. I (probably?) have more logs, though. -- Jon Software Blacksmith -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
