search for: disksizes

Hi, has anyone ever run "make check" from nbd against nbdkit with a python plugin? I usually get segfaults during such a run, and sometimes various other errors happen before the segfault, suggesting that some memory corruption is underway. AFAICS a pure python plugin should not be able to cause memory corruption. Examples of nbdkit logs for running "make check" or subsets of

On 26.09.2016 14:29, Richard W.M. Jones wrote: > On Mon, Sep 26, 2016 at 02:18:02PM +0200, Carl-Daniel Hailfinger wrote: >> Hi, >> >> has anyone ever run "make check" from nbd against nbdkit with a python >> plugin? I usually get segfaults during such a run, and sometimes various >> other errors happen before the segfault, suggesting that some memory

On 26.09.2016 19:20, Carl-Daniel Hailfinger wrote: > On 26.09.2016 14:29, Richard W.M. Jones wrote: >> On Mon, Sep 26, 2016 at 02:18:02PM +0200, Carl-Daniel Hailfinger wrote: >>> Hi, >>> >>> has anyone ever run "make check" from nbd against nbdkit with a python >>> plugin? I usually get segfaults during such a run, and sometimes various

On Mon, Sep 26, 2016 at 02:18:02PM +0200, Carl-Daniel Hailfinger wrote: > Hi, > > has anyone ever run "make check" from nbd against nbdkit with a python > plugin? I usually get segfaults during such a run, and sometimes various > other errors happen before the segfault, suggesting that some memory > corruption is underway. > AFAICS a pure python plugin should not be

Hi! as far as I understood from "xml format for openvz driver" thread available at [1] it should be possible to specify via libvirt disk size and disk inodes for openvz VM.But the following device section in VM xml description doesn't set disksize and diskinodes properly (it looks like those parameters are taken from default OpenVZ config and not as they are specified in

I am trying to build a distribution without having to be root. The SYSLINUX installer typically needs root to do loopback mounting, but if you have MTOOLS, you can use that instead. This seems to work so far: #!/bin/sh # A minimal replacement for /usr/bin/syslinux; assumes that ldlinux.sys # and ldlinux.bss are available in the current directory. You must # specify locations of mkdosfs and

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

I have moved a Samba installation from an old samba 2.2.8a (on a 2.4.21 kernel) to a new server running Samba 3.0.10 on a SuSE 9.2 (kernel 2.6.8) and I now have a problem using the (same) shares from client W2K machines. When I open "My Computer" window on a client, the drives are marked by a red cross, as if they were disconnected, and the disksize is zero. I can decend into the

Zsmalloc is ready for page migration so zram can use __GFP_MOVABLE from now on. I did test to see how it helps to make higher order pages. Test scenario is as follows. KVM guest, 1G memory, ext4 formated zram block device, for i in `seq 1 8`; do dd if=/dev/vda1 of=mnt/test$i.txt bs=128M count=1 & done wait `pidof dd` for i in `seq 1 2 8`; do rm -rf mnt/test$i.txt done

...usefull for removable media like diskettes, Zipdisks, USB Flash keys, etc.. I don't know if the fact that Syslinux is now installed using blockmapping is really breaking the usefullness for harddisks. You already mentioned system attribute will protect from defragmentation tools, but how about disksizes? Isolinux and PXElinux will remain unreplaceable, so it would be most interesting to see most development in every component that is not Syslinux itself. PXElinux, Isolinux, Memdisk, Menu, Sample programs. Since 3.10preX, Memdisk's INITRD can take multiple files. However, can it also take a f...

Hello all, I ran across a couple bugs in memdisk concerning hd images the other day. With the attached patch I've been able to successfully boot a 32MB gzipped hd image. (I'll put the image up for a short while at ftp://ftp.io.com/pub/usr/duanev/fdoshd.img.gz) The pxelinux.cfg entry I'm using is: label fdos kernel memdisk append keeppxe initrd=fdoshd.img.gz

Hi Jens, this series removes the revalidate_disk() function, which has been a really odd duck in the last years. The prime reason why most people use it is because it propagates a size change from the gendisk to the block_device structure. But it also calls into the rather ill defined ->revalidate_disk method which is rather useless for the callers. So this adds a new helper to just

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

When I say busybox it''s actually VMware ESX server which seems to use busybox (which I guess is the case a number of other software appliances) . Reason for wanting to install puppet is to run the cli tools to create nightly vmware snapshots. I''m happy to give it a go (and add the docs to the wiki) but I''m not too sure at this stage how big a task this might be and what,

Hi: I''ve met an ext4 Bug in dom0 kernel 2.6.32.36. (See kernel stack below) 32.36 kernel commit: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=ae333e97552c81ab10395ad1ffc6d6daaadb144a The bug only show up in our cluster environments which includes 300 physical machines, one server will run into this bug per day. Running ontop of every server, there are about 30

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.