On Thu, Sep 15, 2016 at 8:03 AM, Ronan Arraes Jardim Chagas <ronisbr@gmail.com> wrote:
Hi Mauricio,
Em qui, 2016-09-15 às 10:48 -0300, Mauricio Barbosa escreveu:
Did you checked your snapshots that snapper has taken? Maybe here is your problem of "lack of space". If it is the source of the problem delete the ones that is not useful...
snapper list or snapper -c $YOUR_CONFIG list
And if your system is broken after a "zypper dup" why not use the amazing "snapper rollback" feature that OpenSuse folks provided to you?
Yes, actually I reinstalled the system and after just one day I started to see the problem again (only 8 snapshots). This is something weird that no one was able to neither provide me a good explanation about what it is happening nor a workaround until it is fixed.
Good is relative. The explanation thus far is they're working on it, and it is mainly due to a metadata accounting problem. They haven't figured out why it's happening, but Jeff reported on linux-btrfs@ that he can consistently hit it with the btrfs/022 xfstest. He and Josef are presumably sorting through this. File systems are really hard, not least of which is they're really non-determinstic. From the moment they're created they change state as they get used. So there is some combination of things that's managed to get you into this state, and now you're stuck in it with this instance of the file system. That it's happened again after the file system is created new, is pretty damn weird from my perspective because I'd expect others to hit it also. But I don't think it's just you or Jeff wouldn't be hitting it consistently with btrfs/022. So basically, you're just going to have to wait until they have something to report and a fix. And/or reinstall and use XFS or something if you can't wait. *shrug* that is an explanation. It's not a great one for you, but that's where things are at. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org