similar to: [supermin] [PATCH] ext2: check for needed block size

Use the right formatting placeholders, so it gives no warnings also on 32bit platforms. --- src/ext2fs-c.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/ext2fs-c.c b/src/ext2fs-c.c index e45980a..cb9282b 100644 --- a/src/ext2fs-c.c +++ b/src/ext2fs-c.c @@ -31,6 +31,7 @@ #include <limits.h> #include <errno.h> #include <assert.h> +#include

Use an helper struct for holding the ext2_filsys variable, so that can be used to add more data. --- src/ext2fs-c.c | 77 +++++++++++++++++++++++++++++++--------------------------- 1 file changed, 41 insertions(+), 36 deletions(-) diff --git a/src/ext2fs-c.c b/src/ext2fs-c.c index 70755c9..8eab24c 100644 --- a/src/ext2fs-c.c +++ b/src/ext2fs-c.c @@ -52,6 +52,11 @@ /* fts.h in glibc is broken,

Obviously for very large files this is going to be a problem, as well as not being very cache efficient. libext2fs can handle writes to parts of files just fine so copy files in blocks. Also demote the "Permission denied" error to a warning, and add some explanatory text telling people not to use sudo. --- src/ext2fs-c.c | 127 +++++++++++++++++++++++++++++++++++----------------------

We created symlinks in two steps, by creating the empty inode and then calling ext2fs_symlink to populate it. This created broken symlinks where the directory name contained a / character, eg: lrwxrwxrwx 1 root root 7 Nov 26 08:43 /bin -> usr/bin lrwxrwxrwx 1 root root 7 Nov 26 08:43 /lib -> usr/lib lrwxrwxrwx 1 root root 9 Nov 26 08:43 /lib64 -> usr/lib64 lrwxrwxrwx 1

The ext2 filesystem on disk format has two ways to store symlinks. For symlinks >= 60 bytes in length, they are stored as files (so-called "slow symlinks"). For shorter symlinks the symlink is stored in the inode ("fast symlinks"). Previously we only created slow symlinks even if there are shorter than 60 bytes. This didn't matter until recently, when a change went

Signed-off-by: Jie Liu <jeff.liu@oracle.com> --- fs/btrfs/super.c | 10 ++++++++-- 1 files changed, 8 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index 15634d4..16f31e1 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@ -406,7 +406,7 @@ static int btrfs_parse_early_options(const char *options, fmode_t flags, u64 *subvol_rootid, struct

Hi Mikhail, I was trying to figure out how to do the following in compiler driver. 1. mcc16 driver has a -p <device_name> option. Now from this device_name I want to be able to construct a file name like "device_name.o" and pass that to the linker. Unpack_values "p" gives me the device_name, but I do not know how to add ".o" suffix to it. something like:

Hi Sanjiv, On Thu, Nov 19, 2009 at 5:07 AM, Sanjiv Gupta <sanjiv.gupta at microchip.com> wrote: > Hi Mikhail, > > I was trying to figure out how to do the following in compiler driver. > > 1.  mcc16 driver has a -p <device_name> option. Now from this device_name I > want to be able to construct a file name like "device_name.o" and pass that > to the

Hi, the two patches improve the way memory is handled in supermin, by cleanly exiting on memory allocation failures, and free'ing memory when not needed (to keep working and not run out of memory). Pino Toscano (2): Check for failures in memory allocations Free memory buffers when not used src/ext2fs-c.c | 13 +++++++++++-- src/init.c | 13 +++++++++++++ 2 files changed, 24

The ext2 filesystem on disk format has two ways to store symlinks. For symlinks >= 60 bytes in length, they are stored as files (so-called "slow symlinks"). For shorter symlinks the symlink is stored in the inode ("fast symlinks"). Previously we only created slow symlinks even if they are shorter than 60 bytes. This didn't matter until recently, when a change went

Hi, to ease debugging issues with appliances (e.g. when used in libguestfs), using --include-packagelist will add a file containing the list of all the packages used. Thanks, Pino Toscano (3): ext2: add ext2fs_chmod and ext2fs_chown chroot: factor out file copy code Add --include-packagelist src/build.ml | 42 +++++++++++++++++++++++++------ src/chroot.ml | 29

Hi. I am currently debugging an issue with libguestfs in Centos 7.2 (Kernel 3.10.0-327.36.3.el7.x86_64). libguestfs is being called by SaltStack to access a qcow2 image, but it is failing. I have narrowed the issue down to the command below: guestmount -i -a /opt/vm-spinning/salt-mnt/salt-images/pb123/system.qcow2 --rw /tmp/guest/opt.vm-spinning.salt-mnt.salt-images.pb123.system.qcow2 I have

OK..this is driving me nuts. I cannot print from Windoze, consistenly getting a "Access denied; Unable to connect" error message" from my samba print server. Config --- Server: RH9.0 uptodate with patches, errata. Samba 2.2.7 HP OfficeJet K60 - hpoj 0.90-14 Client: Win2K w/sp4 HP OfficeJet K60 driver What I *can* do --- Print just fine on RH9/Samba server to the

On Thu, Jun 25, 2015 at 06:09:55PM -0300, Daniel Henrique Barboza wrote: > Hi, > > I've found a problem with supermin code running in an ibm_powerkvm > ppc64le distro. > > Output of libguestfs-test-tool: > [...] > supermin: version: 5.1.10 [...] > supermin: ext2: populating from base image > supermin: ext2: copying files from host filesystem > supermin:

On Tue, Nov 15, 2016 at 10:11:38AM +0000, Paul Braham wrote: > libguestfs: command: run: /usr/bin/supermin5 > libguestfs: command: run: \ --build > libguestfs: command: run: \ --verbose > libguestfs: command: run: \ --if-newer > libguestfs: command: run: \ --lock /var/tmp/.guestfs-0/lock > libguestfs: command: run: \ --copy-kernel > libguestfs: command: run: \ -f ext2 >

Hi, I've found a problem with supermin code running in an ibm_powerkvm ppc64le distro. Output of libguestfs-test-tool: $ libguestfs-test-tool ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. *

QEMU >= 2.10 started to do mandatory locking. This checks the QMP schema to see if we are using that version of qemu. (Note it is sometimes disabled in downstream builds, and it was also enabled in upstream prereleases with version 2.9.9x, so we cannot just check the version number). --- lib/guestfs-internal.h | 1 + lib/qemu.c | 60

Dear all, actually I installed CentOS 5.4 x86_64 on 11 new Dell R710 servers. It is required to use 5.4 to be covered by the NetApp Interoperability Matrix for use of Snapdrive. All systems spit out the error message mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! at boot time. In dmesg the complete SCSI initialization logging appears as follows: SCSI

Patches 1 & 2 were posted previously here: https://www.redhat.com/archives/libguestfs/2016-May/msg00134.html Patch 3 is a hack so I can test this using my own version of qemu (the `-L ?' stuff is not upstream). Patch 4 is where the real action takes place: Replace the caching of qemu features in blob-like files with a sqlite database. Probably the best way to approach this patch is to

NOTE: Not for upstream, yet. This depends on 3 non-upstream patches. - The qemu rework in libguestfs, which in turn depends on what Pino is up to. - Support for '-L ?' in qemu: https://lists.gnu.org/archive/html/qemu-devel/2016-05/threads.html#02596 - Support for bios-fast.bin in qemu: https://lists.gnu.org/archive/html/qemu-devel/2016-05/threads.html#02408 This commit