How to keep track of changes in /etc/
I would like to keep track of changes in /etc/
btrfs
Can btrfs track / avoid bad blocks?
I have a HDD which I don’t entirely trust, but still want to use (burstcoin mining, where if I get a bad block in a file, I’ll only lose a few cents).
Practical limit on the number of btrfs snapshots?
I am considering using btrfs on my data drive so that I can use snapper, or something like snapper, to take time based snapshots. I believe this will let me browse old versions of my data. This would be in addition to my current off site backup since a drive failure would wipe out the data and the snapshots.
How to get rid of the “scanning for btrfs file systems” at start-up?
After upgrading from Ubuntu 12.04 to Ubuntu 12.10, I get a message “scanning for btrfs file systems” at starting-up. I don’t have any BTRFS filesystem. It delays the booting for about 15 seconds.
btrfs ERROR: error during balancing – No space left on device
My Kubuntu 12.04 system ran out of space on on the root partition and will not boot. The command df -h shows a lot of space available (with only 37% used):
How to verify a file copy is reflink/CoW?
I’m playing with btrfs, which allows cp --reflink to copy-on-write. Other programs, such as lxc-clone, may use this feature as well. My question is, how to tell if a file is a CoW of another? Like for hardlink, I can tell from the inode number.
Btrfs RAID1: How to replace a disk drive that is physically no more there?
I have a btrfs RAID1 system with the following state:
What are the advantages of Btrfs for end users?
Btrfs has begun to gain some momentum in replacing ext4 as the default filesystem of choice for a few distributions such as Fedora Core 16. It is experimentally available in a number of other distributions (From Wikipedia: openSUSE 11.3, SLES 11 SP1, Ubuntu 10.10, Sabayon Linux, RHEL6,MeeGo, Debian 6.0, and Slackware 13.37). I’m certainly not ready to convert all my workplace servers over (my file system choice is generally conservative), I’m considering using it at home and on select non-mission critical production machines at work.
Why does rename() take longer when fsync() is called first?
In this test, why does rename() take longer when fsync() is called first?
How to make a btrfs snapshot writable?
According to the btrfs Readonly snapshots patch it’s possible to “set a snapshot readonly/writable on the fly.” So I should be able to turn my readonly snapshot (created with btrfs snapshot -r) writable, somehow.