"free space cache generation" ?
Hi there,
I noticed my syslog is filling up with tons of:
btrfs: free space inode generation (0) did not match free space cache generation (25326)
...any clue ?
TIA.
Quoted 7 lines · Swâmi Petaramesh
Hi there,
I noticed my syslog is filling up with tons of:
btrfs: free space inode generation (0) did not match free space cache generation (25326)
Yeah I need to just put those under a DEBUG ifdef, they aren't a big deal, just letting you know that the on disk cache is invalid and it will have to put it together ye olde fashioned way. Thanks,
Josef
Quoted 3 lines · Josef Bacik
Yeah I need to just put those under a DEBUG ifdef, they aren't a big deal, just letting you know that the on disk cache is invalid and it will have to put it together ye olde fashioned way.
...But is it supposed to, and how to fix it ?
Signature · 2 lines
Swâmi Petaramesh <[email protected]> http://petaramesh.org PGP 9076E32E Ne cherchez pas : Je ne suis pas sur Facebook.
Quoted 6 lines · Swâmi Petaramesh
Quoted 3 lines · Josef Bacik
Yeah I need to just put those under a DEBUG ifdef, they aren't a big deal, just letting you know that the on disk cache is invalid and it will have to put it together ye olde fashioned way.
...But is it supposed to, and how to fix it ?
It can happen for all sorts of different reasons. Did you have a unclean unmount at some point? Do you have a particularly full file system? I recently increased the size of the free space cache, so if you are not on a kernel with that patch you are more likely to run out of space while writing out free space cache and run into this problem. Thanks,
Josef
Quoted 2 lines · Josef Bacik
It can happen for all sorts of different reasons. Did you have a unclean unmount at some point?
Not that I'm aware of...
Quoted 1 line
Do you have a particularly full file system?
~1 TB FS, 23% full...
Only, I have several Linux distros installed on the same BTRFS - in different subvols - so I sometimes mount it with a 3.5.x kernel, and more rarely - but sometimes - with a 3.2.x...
=> Also I have to mention that I have lost a complete BTRFS FS, that was a /boot with snapshots. At some point it started to fail mounting, the kernel complaining that some trees (corresponding to removed snapshots as far as I could tell) were b0rked, and btrfsck couldn't help...
So I lost the FS - and lost quite a bit of confidence into BTRFS the same day... :-\
Signature · 2 lines
Swâmi Petaramesh <[email protected]> http://petaramesh.org PGP 9076E32E Ne cherchez pas : Je ne suis pas sur Facebook.
Quoted 6 lines · Swâmi Petaramesh
Quoted 2 lines · Josef Bacik
It can happen for all sorts of different reasons. Did you have a unclean unmount at some point?
Not that I'm aware of...
Quoted 8 lines
Quoted 1 line
Do you have a particularly full file system?
~1 TB FS, 23% full...
Only, I have several Linux distros installed on the same BTRFS - in different subvols - so I sometimes mount it with a 3.5.x kernel, and more rarely - but sometimes - with a 3.2.x...
Well I think I changed the space cache format between those releases which would cause them all to be discarded and remade.
Quoted 8 lines
=> Also I have to mention that I have lost a complete BTRFS FS, that was a /boot with snapshots. At some point it started to fail mounting, the kernel complaining that some trees (corresponding to removed snapshots as far as I could tell) were b0rked, and btrfsck couldn't help...
So I lost the FS - and lost quite a bit of confidence into BTRFS the same day... :-\
Yes well, welcome to using an experimental file system.
Josef