search for: disksiz

...fore 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 it from nbd against nbdkit: nbdkit -n -f python script=ssd-ftl-wearleveling.py disksize=52428800 nbdkit: python[6]: error: ssd-ftl-wearleveling.py: callback failed: close nbdkit: python[7]: error: invalid flush request: expecting offset and length == 0 nbdkit: python[7]: error: write reply: Connection reset by peer Segmentation fault nbdkit -n -f python script=ssd-ftl-wearleveling.p...

...#39;t segfault ever. > > Did you get a stack trace from C (not from Python)? The core files were useless, but I ran nbdkit in gdb and got something... (gdb) run -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 Starting program: /software/nbdkit/src/nbdkit -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_6...

...>> >> Did you get a stack trace from C (not from Python)? > The core files were useless, but I ran nbdkit in gdb and got something... > > (gdb) run -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 > Starting program: /software/nbdkit/src/nbdkit -n -f /software/nbdkit/plugins/python/.libs/nbdkit-python-plugin.so script=/software/nbdkit/plugins/python/ssd-ftl-wearleveling.py disksize=52428800 > [Thread debugging using libthread_db enabled] > Using host libthread_db library &...

...cause memory corruption, and nbdkit shouldn't segfault ever. Did you get a stack trace from C (not from Python)? Rich. > Examples of nbdkit logs for running "make check" or subsets of it from > nbd against nbdkit: > > nbdkit -n -f python script=ssd-ftl-wearleveling.py disksize=52428800 > nbdkit: python[6]: error: ssd-ftl-wearleveling.py: callback failed: close > nbdkit: python[7]: error: invalid flush request: expecting offset and > length == 0 > nbdkit: python[7]: error: write reply: Connection reset by peer > Segmentation fault > > nbdkit -n -f p...

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 libvirt tags): <devices> <filesystem type='template'> <source name='centos-5-x86'/> <target dir='/'/&gt...

...he # image will be overwritten if it exists, and an empty boot disk image # will be created. To avoid overwriting existing files, just omit # the two steps marked "Create fresh image" below. # General configuation IMAGE=`pwd`/lnx.img TEMP=bootsector.tmp MKDOSFS=mkdosfs MCOPY=mcopy DD=dd DISKSIZE=1440 # MTOOLS configuration LETTER=Q CONFIG="drive $LETTER: file=\"$IMAGE\" #TEMP" MTOOLSRC=~/.mtoolsrc grep drive.$LETTER ~/.mtoolsrc >/dev/null 2>&1 || echo $CONFIG >> ~/.mtoolsrc # ### Create fresh image $DD if=/dev/zero of=$IMAGE bs=1k count=$DISKSIZE $MK...

...s_mdi * mdi) { + const char * cmdline; + + if (!show_info) + return; + + cmdline = MK_PTR( + mdi->cmdline.seg_off.segment, + mdi->cmdline.seg_off.offset + ); + printf( + "Found MEMDISK version %u.%02u:\n" + " diskbuf == 0x%08X, disksize == %u sectors\n" + " bootloaderid == 0x%02X (%s),\n" + " cmdline: %s\n", + mdi->version_major, + mdi->version_minor, + mdi->diskbuf, + mdi->disksize, + mdi->bootloaderid, + bootloadername(mdi->boot...

...a (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 folders on the drives, and here all the files are there as expected. After opening the "My Computer" window, a panic error message is logged in log.smbd. The error message is added below. As long as I'm in a Samba share, the error message is reapeated...

...insertions(+), 2 deletions(-) diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c index 370c2f76016d..10f6ff1cf6a0 100644 --- a/drivers/block/zram/zram_drv.c +++ b/drivers/block/zram/zram_drv.c @@ -514,7 +514,8 @@ static struct zram_meta *zram_meta_alloc(char *pool_name, u64 disksize) goto out_error; } - meta->mem_pool = zs_create_pool(pool_name, GFP_NOIO | __GFP_HIGHMEM); + meta->mem_pool = zs_create_pool(pool_name, GFP_NOIO|__GFP_HIGHMEM + |__GFP_MOVABLE); if (!meta->mem_pool) { pr_err("Error creating memory pool\n"); goto out_error; di...

...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...

...ov ebx,[es:si+16] .got_address: cmp dword [es:si+12],0 ; LBA too large? jne .overrun movzx ecx, word [es:si+2] ; Sectors to transfer - mov edi,[es:si+8] ; Starting sector - mov eax,edi + mov esi,[es:si+8] ; Starting sector + mov eax,esi add eax,ecx jc .overrun cmp eax,[DiskSize] ja .overrun shl ecx,SECTORSIZE_LG2-2 ; Convert to dwords - shl edi,SECTORSIZE_LG2 ; Convert to an offset - add edi,[DiskBuf] + shl esi,SECTORSIZE_LG2 ; Convert to an offset + add esi,[DiskBuf] + mov edi,ebx pop es ret

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

...t edd_dpt { uint8_t chksum; /* DPI checksum */ } __attribute__((packed)); +struct mBFT { + struct acpi_description_header acpi; + uint32_t safe_hook; /* "Safe hook" physical address */ +} __attribute__((packed)); + struct patch_area { uint32_t diskbuf; uint32_t disksize; @@ -816,6 +834,7 @@ void setup(const struct real_mode_args *rm_args_ptr) unsigned int bin_size; char *memdisk_hook; struct memdisk_header *hptr; + struct safe_hook *safe_hook; struct patch_area *pptr; uint16_t driverseg; uint32_t driverptr, driveraddr; @@ -899,6 +...

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,

...get_blocks_flags; 2223 <+++struct buffer_head new; 2224 <+++sector_t next = mpd->b_blocknr; 2225 <+++unsigned max_blocks = mpd->b_size >> mpd->inode->i_blkbits; 2226 <+++loff_t disksize = EXT4_I(mpd->inode)->i_disksize; 2227 <+++handle_t *handle = NULL; 2228 Could it be possilbe, right now I am tring to reproduce this problem in a much easiler way, any suggestion? Many thanks. ------------[ cut here ]------------ kernel BUG at fs/ext4/extents.c:1716! invalid...

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.