On 11/30/2014 10:37 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-12-01 02:28, Roman Bysh wrote:
On 11/30/2014 03:59 PM, Carlos E. R. wrote:
Message I got:
Backrefs don't agree with each other and extent record doesn't agree with anybody, so we can't fix bytenr 592625664 bytes 16384 failed to repair damaged filesystem, aborting.
I also ran btrfs check --repair /dev/sda1 Same error showed up. Since this is my main machine I reinstalled using ext4.
LOL. I can't convince you to try again, because I'd probably do the same as you did...
I decided that I'll wait another two or three years until the btrfs and btrfs patches for the kernel are more mature.
For now, I'll test and practice btrfs on VirtualBox. It's much safer.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlR74nYACgkQtTMYHG2NR9U8EACfQuuWCZbh1SXi9BdEmP1NlOZS Ln4AmwS0D7ea4E/RU+aHNNefSWyXof5T =eT6J -----END PGP SIGNATURE-----
I really wanted to like btrfs. IMHO Snapper is silently taking way too many snapshots. I think that a snapshot message should pop up letting the user know. Otherwise I have to go in and delete a lot of the snapshots.
I cannot see the size of the snapshots in snapper only in console text. It should create a pre after the installation and post after the updates.
Why does the ID number start at 300? Interesting. I've seen examples where it starts at 1.
Tomorrow, I'm going to order a 1TB drive. How much space should I assign for root when using btrfs?