similar to: [PATCH nbdkit v3 0/5] partition filter: Support MBR logical partitions.

This is a revised version of the two series previously posted here: https://www.redhat.com/archives/libguestfs/2019-January/msg00137.html https://www.redhat.com/archives/libguestfs/2019-January/msg00139.html There have been many smaller changes but the highlights are: - Using SECTOR_SIZE instead of hard-coding 512 everywhere. - Additional safety checks that the EBR chain doesn't jump

This implements support for MBR logical partitions in nbdkit-partition-filter, complementing existing support in the partitioning plugin. Rich.

v1 was here: https://www.redhat.com/archives/libguestfs/2019-January/thread.html#00198 For v2 I changed most existing prerequisite tests to use the new mechanism. I only changed simple tests. There are a few more complex tests that don't fit the “requires model” and those are not changed. I normalized qemu-io/qemu-img testing to always use the --version flag, where previously we used a mix

I only did a handful of the tests to demonstrate the point. If the patch approach is accepted then I'll do the remainder of the tests in v2. Rich.

--- filters/partition/nbdkit-partition-filter.pod | 5 - filters/partition/partition-mbr.c | 105 +++++++++++++++++- tests/test-partitioning1.sh | 22 +++- 3 files changed, 121 insertions(+), 11 deletions(-) diff --git a/filters/partition/nbdkit-partition-filter.pod b/filters/partition/nbdkit-partition-filter.pod index 4a615b6..ccd1b52 100644 ---

--- tests/functions.sh.in | 17 ++++++++++++++++- tests/test-cache-max-size.sh | 18 +++--------------- tests/test-data-7E.sh | 8 ++------ tests/test-data-base64.sh | 12 ++++-------- tests/test-data-file.sh | 8 ++------ tests/test-data-raw.sh | 8 ++------ tests/test-eflags.sh | 13

On 1/21/19 12:15 PM, Richard W.M. Jones wrote: > --- > filters/partition/nbdkit-partition-filter.pod | 5 - > filters/partition/partition-mbr.c | 105 +++++++++++++++++- > tests/test-partitioning1.sh | 22 +++- > 3 files changed, 121 insertions(+), 11 deletions(-) > > @@ -69,16 +75,16 @@ find_mbr_partition (struct nbdkit_next_ops *next_ops,

I have 4 systems and each one of them has a partition I'd like to be remotely accessible on the other 3 systems. In other words System1 has Partition1. Systems 2,3,4 should be able to remotely mount Partition1 from System1. Also System2 has Partition2. Then systems 1,3,4 should be able to remotely mount Partition2 from System2 and so on. I tried NFS and it works but only in the ideal

nbdkit partitioning boot.img swap.img root.img ... creates a virtual disk by adding a partition table. In ancient times Xen used to do this. Rich.

The partitioning plugin patch is the same (except for rebasing). However I have changed the first two patches based on feedback received. In particular this fixes a very serious bug found by Eric Blake in the current truncate filter. Rich.

Since both the partitioning plugin and partition filter now support MBR logical partitions, the original test for GPT (test-partitioning4.sh) can be duplicated and modified to test MBR. --- tests/Makefile.am | 4 +- tests/test-partitioning4.sh | 2 +- tests/test-partitioning6.sh | 92 +++++++++++++++++++++++++++++++++++++ 3 files changed, 96 insertions(+), 2 deletions(-) diff --git

An evolution of the patch I posted yesterday to qemu-devel (https://www.mail-archive.com/qemu-devel@nongnu.org/msg588920.html) which (a) works and (b) has a test. Rich.

I am trying to install R-2.3.0 on a 64bit linux box and encounter several error during the make step. I'd appreciate any help. Error messages follow: [root at calculon R-2.3.0]# make make[4]: Entering directory `/state/partition1/apps/packages/R-2.3.0/src/modules/lapack' gcc -shared -L/usr/local/lib64 -o libRlapack.so dlamc.o dlapack0.o dlapack1.o dlapack2.o dlapack3.o cmplx.o

I have a windows server with a 250G drive the drive is partitioned as follows. partition 1: dell utility partition partition 2: fat32 windows c: partition partition 3: extended partition partition 5: logical NTFS partitition. NTFS partition was setup with 220G. but only about 18G was being used, so i shrank NTFS down to 50G. now i want to make a drive image to create a HVM domain. how can

I think this is likely a bug with either mount or glusterfs: [root at vm-container-0-0 ~]# cat /etc/fstab LABEL=/ / ext3 defaults 1 1 LABEL=/state/partition /state/partition1 ext3 defaults 1 2 LABEL=/var /var ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults

--- tests/functions.sh.in | 17 ++++++++++++++++- tests/test-memory-largest.sh | 8 ++------ tests/test-partition1.sh | 22 ++++------------------ tests/test-partition2.sh | 6 +----- tests/test-pattern-largest.sh | 8 ++------ 5 files changed, 25 insertions(+), 36 deletions(-) diff --git a/tests/functions.sh.in b/tests/functions.sh.in index 35647f7..97afbbf 100644 ---

Hello, I would like to find out the topology of an existing volume. For example, if I have a distributed replicated volume, what bricks are the replication partners? Fred -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121114/b203ea91/attachment.html>

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

1) code split and move Iterator related functionality is yanked from chain.c and moved to iterator.{c,h}. Both are moved to com32/chain and this way chain.c is ready for further splitting. Alternatively, partiter could be moved to com32/lib at any time in the future. It's potentially useful for other modules (e.g. if someone wanted to code partition dumper or editor). 2) Iterator updates

This was a rather longer trip around the houses than I anticipated! The basic purpose of the patch series is to set $nbdkit_stdio_safe to "0" or "1" in sh and eval plugin scripts. To do that, I ended up adding a nicer way to manipulate environ lists, and to do that, I ended up adding a whole generic vector implementation which is applicable in a lot of different places.