I also had some problems with syslinux.
For me it only works if I put boot folder to root of btrfs.
Didn't have a chance to do more test, but I copied /boot from default
subvolume to subvolume 0 and it boots OK.
----------
regards
Blaz Balon
On 01/31/2014 11:00 PM, Alex wrote:
Sorry KC:
All my VM's are on syslinux (actually extlinux) and btrfs:
Device Boot Start End Blocks Id System
/dev/vda1 * 2048 7938047 3968000 83 Linux
/dev/vda2 7938048 8388607 225280 82 Linux swap / Solaris
root@<VM> ~ # ll /boot
total 19452
-rw-r--r-- 1 root root 2319932 Jan 21 06:12 System.map-3.12-1-amd64
-rw-r--r-- 1 root root 149029 Jan 21 06:12 config-3.12-1-amd64
drwxr-xr-x 1 root root 176 Jan 28 22:32 extlinux/
-rw-r--r-- 1 root root 14240605 Jan 28 22:32 initrd.img-3.12-1-amd64
-rw-r--r-- 1 root root 176764 Nov 13 2011 memtest86+.bin
-rw-r--r-- 1 root root 178944 Nov 13 2011 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 2842064 Jan 21 06:08 vmlinuz-3.12-1-amd64
root@china ~ #
Occasionally I get excited and decide to fix it 'til it breaks (usually I
turn compression on, and /boot can't be accessed), but it's been working
fine for a few years now.
Kind regards.
Al.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
