These patches can be tested from here:
https://launchpad.net/~cheako/+archive/ubuntu/boot-subvol
Code from here:
https://github.com/cheako/os-prober/tree/aggregate
Here are corrected versions of these patches. Filesystem raid is
almost certainly a separate bug.
From 3d4b580dea4592793af3411fc0543af36de0e958 Mon Sep 17 00:00:00 2001
From: Michael Mestnik
Date: Fri, 9 Jun 2017 13:04:05 -0500
Subject: [PATCH 2/6] Process filesystem raid entries
---
common.sh
Using these patches reveals they are not complete, there are two areas
that need to be addressed.
Firstly the kernel can and will use any device in a filesystem for the
contents of /proc/mount. This causes problems in multiple areas that
os-probe will have to compensate for.
Second 50mounted-tes
Hello,
This is the result of several days working the issues and analysing
each aspect. These patches include only what is necessary to support
subvol. Care has been taken to future proof by preparing for other
filesystems, currently this only works with btrfs. These patches have
been split, s
Forget about all of this, I'm going to simplify the design. I have in
mind to make the following changes.
1. Don't just change $1 from being the path of a block device to being
a reserved word.
a. Instead append an additional parameter.
2. Use subvolume id, instead of names.
The patches have changes that have nothing to do with btrfs, I'll
attempt to isolate these.
The patches introduce a bug.
/usr/lib/os-probes/50mounted-tests
calls fs_type on "btrfs"
I'll look into this some more.
Refresh and simplify the patches.
https://github.com/cheako/os-prober/tree/btrfs-subvol
Also note os-probe fork:
https://github.com/campadrenalin/os-prober/commit/b571c0c7c3fe8986cc17dd200173fb7d86ef0c24
This commit reorgs the project making merges with the fork difficult.
From af1753acff410e69844
On Fri, 11 Jan 2013 12:34:20 -0500 Gene Czarcinski wrote:
This was found on Fedora 18.
Both os-prober and linux-boot-prober do not support root, boot, or
root+boot on a btrfs subvolume.
The attached patch corrects that. It supplies information such that
grub2, with an additional small patch,
Christian PERRIER (04/02/2013):
> Do you think it would be OK to already commit this is the master
> branch so that these important contributions are not simply forgotten
> when we really start working on jessie (in a year or so...:-( ).
>
> Of course, if we do this, we fork a wheezy branch "just
On 02/04/2013 01:03 AM, Christian PERRIER wrote:
Quoting Cyril Brulebois (k...@debian.org):
Hi Gene,
Gene Czarcinski (11/01/2013):
This was found on Fedora 18.
Both os-prober and linux-boot-prober do not support root, boot, or
root+boot on a btrfs subvolume.
thanks for the patch; I'm afraid
Quoting Cyril Brulebois (k...@debian.org):
> Hi Gene,
>
> Gene Czarcinski (11/01/2013):
> > This was found on Fedora 18.
> >
> > Both os-prober and linux-boot-prober do not support root, boot, or
> > root+boot on a btrfs subvolume.
>
> thanks for the patch; I'm afraid it's too huge for us to re
Hi Gene,
Gene Czarcinski (11/01/2013):
> This was found on Fedora 18.
>
> Both os-prober and linux-boot-prober do not support root, boot, or
> root+boot on a btrfs subvolume.
thanks for the patch; I'm afraid it's too huge for us to review/merge
at this late stage of the release cycle; it should
This was found on Fedora 18.
Both os-prober and linux-boot-prober do not support root, boot, or
root+boot on a btrfs subvolume.
The attached patch corrects that. It supplies information such that
grub2, with an additional small patch, will not handle btrfs in
30_os-prober.
I have attached
Package: os-prober
Version: 1.55
Grub and the working environment are installed on a btrfs subvolume.
update-grub does not find any other linux systems on different
subvolumens (same btrfs filesystem).
To reproduce on debian with btrfs-tools:
Have a spare device, say /dev/sdc1
mkfs.btrfs /dev/sdc1
15 matches
Mail list logo
