Quote:
Originally Posted by
particleman72
can you mount rw after boot?
# mount -o remount,rw /;
I did already say I could
Quote:
Originally Posted by
gonX
Post fstab (cat /etc/fstab) and post the last 100 lines of dmesg (dmesg | tail -n 100) after boot.
The last 100 lines wouldn't be of much use as that's all just wifi and other such crap. There is this further up though:
Code:
Code:
$ dmesg | egrep -i "(btrfs|sda)"
[ 0.000000] Command line: root=/dev/sda1 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
[ 0.000000] Kernel command line: root=/dev/sda1 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
[ 1.412671] sd 0:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
[ 1.412745] sd 0:0:0:0: [sda] Write Protect is off
[ 1.412749] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.412782] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.414982] sda: sda1
[ 1.415445] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.487440] Btrfs loaded
[ 1.488171] device fsid b9a11d9a-7db6-46c3-b2f4-9b651f3e108b devid 1 transid 395 /dev/sda1
[ 1.806315] device fsid b9a11d9a-7db6-46c3-b2f4-9b651f3e108b devid 1 transid 395 /dev/sda1
[ 2.245862] device fsid b9a11d9a-7db6-46c3-b2f4-9b651f3e108b devid 1 transid 395 /dev/sda1
[ 2.460893] device fsid b9a11d9a-7db6-46c3-b2f4-9b651f3e108b devid 1 transid 395 /dev/sda1
[ 2.461807] btrfs: disk space caching is enabled
[ 2.463332] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields.
[ 2.463794] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields.
[ 2.480639] Btrfs detected SSD devices, enabling SSD mode
[ 2.481025] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields.
[ 5.786825] device fsid b9a11d9a-7db6-46c3-b2f4-9b651f3e108b devid 1 transid 397 /dev/sda1
[ 5.787612] btrfs: disk space caching is enabled
[ 5.809776] Btrfs detected SSD devices, enabling SSD mode
[ 5.809797] btrfs: mismatching generation and generation_v2 found in root item. This root was probably mounted with an older kernel. Resetting all new fields.
[ 6.465721] device fsid b9a11d9a-7db6-46c3-b2f4-9b651f3e108b devid 1 transid 397 /dev/sda1
[ 25.171509] btrfs: disk space caching is enabled
Code:
Code:
#UUID=58a3c64f-ba75-4f44-bad2-a24b05331b6a / btrfs defaults,compress,ssd,discard 0 0
UUID=/dev/sda1 / btrfs defaults,noatime,discard,ssd,compress 0 0
I've just noticed that I've garbled up the fstab (used a block device against UUID), so going to fix that and reboot
[edit]
yeah that fixed it. Dumb mistake. I can't believe I missed that yesterday. Still, I did suspect it was something stupid I'd overlooked.
Thanks for your help
Quote:
Originally Posted by
CaptainBlame
You used a file system conversion tool; you are braver than me
I know what you mean. I'm hoping to convert my work desktop to Btrfs to take advantage of snapshotting, however I thought I'd better check the conversion tool at home (where it matters less) first. Plus I wanted to get the feel of just how mature Btrfs is before committing to it.
Honestly though, even just with these little tests (and I'm not in any way blaming the booting in read only on Btrfs), I'm largely unimpressed. It's pretty obvious from using it that it's designed to be a copy of ZFS, yet the CLI tools aren't near as clean and user friendly. I honestly do wish Oracle (or whoever's decision it was) just wrote new ZFS drivers for Linux instead of trying to reinvent a crappier version of ZFS.