Hi All, It seems my btrfs file space cache is corrupt; I had to run clear the log through a kernel problem. I''ve seen messages that the cache is rebuilt automatically, but this doesn''t seem to be true as the messages that the free space is what is expected keep coming. I''m running kernel 3.8.2 (Siduction) on Debian testing. As a subsidiary question, please, should the <pass> value in fstab be zero or non-zero? Kind regards. Al. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Alex, On 03/13/2013 01:17 AM, Alex wrote:> Hi All, > > It seems my btrfs file space cache is corrupt; I had to run clear the log > through a kernel problem. > > I''ve seen messages that the cache is rebuilt automatically, but this doesn''t > seem to be true as the messages that the free space is what is expected keep > coming. > > I''m running kernel 3.8.2 (Siduction) on Debian testing.I believe you may try clear_cache mount option https://btrfs.wiki.kernel.org/index.php/Mount_options> > As a subsidiary question, please, should the <pass> value in fstab be zero or > non-zero?It should be zero. But since fsck.btrfs is non-existent, it does not really matter I guess. ~dima> Kind regards. > > Al. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Mar 13, 2013 at 02:31:27PM +0900, dima wrote:> Hello Alex, > > On 03/13/2013 01:17 AM, Alex wrote: > >Hi All, > > > >It seems my btrfs file space cache is corrupt; I had to run clear the log > >through a kernel problem. > > > >I''ve seen messages that the cache is rebuilt automatically, but this doesn''t > >seem to be true as the messages that the free space is what is expected keep > >coming. > > > >I''m running kernel 3.8.2 (Siduction) on Debian testing. > > > I believe you may try clear_cache mount option > https://btrfs.wiki.kernel.org/index.php/Mount_options > > > > > >As a subsidiary question, please, should the <pass> value in fstab be zero or > >non-zero? > > > It should be zero. But since fsck.btrfs is non-existent, it does not > really matter I guess.Eh? We''ve had a functional btrfsck for nearly a year. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- But somewhere along the line, it seems / That pimp became --- cool, and punk mainstream.
On 03/13/2013 05:53 PM, Hugo Mills wrote:> On Wed, Mar 13, 2013 at 02:31:27PM +0900, dima wrote: >> Hello Alex, >> >> On 03/13/2013 01:17 AM, Alex wrote: >>> Hi All, >>> >>> It seems my btrfs file space cache is corrupt; I had to run clear the log >>> through a kernel problem. >>> >>> I''ve seen messages that the cache is rebuilt automatically, but this doesn''t >>> seem to be true as the messages that the free space is what is expected keep >>> coming. >>> >>> I''m running kernel 3.8.2 (Siduction) on Debian testing. >> >> >> I believe you may try clear_cache mount option >> https://btrfs.wiki.kernel.org/index.php/Mount_options >> >> >>> >>> As a subsidiary question, please, should the <pass> value in fstab be zero or >>> non-zero? >> >> >> It should be zero. But since fsck.btrfs is non-existent, it does not >> really matter I guess. > > Eh? We''ve had a functional btrfsck for nearly a year.Right. But it is not something that you run on boot, is it. That is why I mentioned fsck.btrfs> Hugo. >-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html