search for: mballoc

We are running a benchmark that does single threaded 512 KB writes to a LUN on a CLARiiON storage array. The dual Xeon host (Dell 2650) with 4 GB of memory runs RHEL 4U3 We measured the write bandwidth for writes to the block device corresponding to the lun (e.g. /dev/sdb), a file in an ext2 filesystem and to a file in an ext3 file system. Write b/w for 512 KB writes Block device 312 MBps Ext2

Hi, I could not find this anywhere else reported, so here we go: creating a new btrfs filesystem (btrfs-progs-unstable from git) and mounting it succeeds, unmounting however fails with the kernel messages attached to this mail. After that, I can still read and write to the btrfs mount, but e.g. /bin/sync never finishes, sysrq-s never reports "Sync complete". I''m using a

Hi, I get the following error when I try to mount lustre on the clients. Permanent disk data: Target: lustre-OSTffff Index: unassigned Lustre FS: lustre Mount type: ldiskfs Flags: 0x72 (OST needs_index first_time update ) Persistent mount opts: errors=remount-ro,extents,mballoc Parameters: mgsnode=164.107.119.231 at tcp sh: losetup: command not found mkfs.lustre: error 32512 on losetup: Unknown error 32512 mkfs.lustre FATAL: Loop device setup for /dev/sdb failed: Unknown error 32512 Connection to wci70 closed. mount.lustre: mount /dev/sdb at /tmp/ost failed: Block devic...

...iers enabled [ 242.302098] kjournald2 starting: pid 2509, dev cciss!c0d0p8:8, commit interval 5 seconds [ 242.311272] EXT4 FS on cciss!c0d0p8, internal journal on cciss!c0d0p8:8 [ 242.311331] EXT4-fs: delayed allocation enabled [ 242.311386] EXT4-fs: file extents enabled [ 242.311562] EXT4-fs: mballoc enabled [ 242.311627] EXT4-fs: mounted filesystem cciss!c0d0p8 with writeback data mode [ 242.329741] EXT4-fs: barriers enabled [ 242.337949] kjournald2 starting: pid 2510, dev cciss!c0d0p9:8, commit interval 5 seconds [ 242.343248] EXT4 FS on cciss!c0d0p9, internal journal on cciss!c0d0p9:8 [...

All, I'm requesting comments from the expert readers of ext3-users on these notes for tuning ext3 for performance. Most helpful would be feedback pertinent to RHEL 5; as XFS isn't supported under Red Hat Enterprise Linux these items are an attempt to match XFS performance with ext3. These items were culled from a number of sources. Will they be effective for achieving the performance

Hello, I have a production script that do read operations to a lot of small files. I read that one can gain performance boost with small files by using a loop device on top of Lustre. So a created 500 GB file striped across all of my OSTs(which are 8). I formatted the file with ext2 fs, and mounted it on a client. Just for the sake of testing a simple bash script finds all files with a given file

...l ><rescue> mount /dev/vg_f11x64/lv_root /sysroot EXT4-fs (dm-0): barriers enabled kjournald2 starting: pid 269, dev dm-0:8, commit interval 5 seconds EXT4-fs (dm-0): internal journal on dm-0:8 EXT4-fs (dm-0): delayed allocation enabled EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs (dm-0): mounted filesystem with ordered data mode ><rescue> ls /sysroot/ bin dev home lib64 media opt root selinux sys usr boot etc lib lost+found mnt proc sbin srv tmp var ><rescue> exit I'd really like to know how to g...

...of our OSTs remounted and went through the recovery window but clients hang trying to access them. Also /proc/fs/lustre/obdfilter/$UUID/ is empty for that OST UUID. LDISKFS FS on dm-5, internal journal on dm-5:8 LDISKFS-fs: delayed allocation enabled LDISKFS-fs: file extents enabled LDISKFS-fs: mballoc enabled LDISKFS-fs: mounted filesystem dm-5 with ordered data mode Lustre: 16377:0:(filter.c:990:filter_init_server_data()) RECOVERY: service scratch-OST0007, 281 recoverable clients, 0 delayed clients, last_rcvd 55834575088 Lustre: scratch-OST0007: Now serving scratch-OST0007 on /dev/mapper/ost_sc...

...ount, and stripe are taken from the files above (not shown in this email) when the volumes were first created. 309 mkfs.lustre --ost --mgsnode=10.10.1.140@tcp0 --fsname=umt3 --reformat --index=35 \ --mkfsoptions="-i 2000000" --reformat --mountfsoptions="errors=remount-ro,extents,mballoc,stripe=256" /dev/sdc The UUID here is taken from the /etc/fstab, where the entry has been commented out until we are ready to again use the volume 310 tune2fs -O uninit_bg -m 1 -U 02bcb3d2-ad48-4992-ba71-7b48787defea /dev/sdc 311 e2fsck -fy /dev/sdc 312 mount -t ldiskfs /dev/sdc...

My application always needs to sync file data after writing. I don't want anything handing around in the kernel buffers. I am wondering what is the best method to accomplish this. 1. Do I use EXT2 and use fdatasync() or fsync()? 2. Do I use EXT2 and mount with the "sync" option? 3. Do I use EXT2 and use the O_DIRECT flag on open()? 4. Do I use EXT3 in full journaled mode,

I'm setting up a new file server and I just can't seem to get the expected performance from ext3. Unfortunately I'm stuck with ext3 due to my use of Lustre. So I'm hoping you dear readers will send me some tips for increasing ext3 performance. The system is using an Areca hardware raid controller with 5 7200RPM SATA disks. The RAID controller has 128MB of cache and the disks

...ailout" /dev/sdb checking for existing Lustre data: found CONFIGS/mountdata Reading CONFIGS/mountdata Read previous values: Target: lustre-OST0027 Index: 39 Lustre FS: lustre Mount type: ldiskfs Flags: 0x2 (OST ) Persistent mount opts: errors=remount-ro,extents,mballoc Parameters: failover.mode=failout mgsnode=192.168.16.122 at tcp tunefs.lustre: cannot change the name of a registered target tunefs.lustre: exiting with 1 (Operation not permitted) <snap> The purpose of tunefs.lustre is not clear from the docs. The continuation from this point of "erro...

...ext4dev using e2fsprogs 1.40.8-2 mke2fs -q -j /dev/mapper/dualvg0-foo -E test_fs mount /dev/mapper/dualvg0-foo /mnt/ -t ext4dev EXT4 FS on dm-12, internal journal EXT4-fs: mounted filesystem with ordered data mode. EXT4-fs: file extents enabled EXT4-fs: mballoc enabled ./usr/kinit/fstype/shared/fstype /dev/mapper/dualvg0-foo FSTYPE=ext4dev FSSIZE=1073741824 as bonus fix ext3_super_block to latest definition. Signed-off-by: maximilian attems <max at stro.at> diff --git a/usr/kinit/fstype/ext3_fs.h b/usr/kinit/fstyp...

...e --fsname datafs --ost --mgsnode=pool4 at tcp --reformat / dev/sda2 Permanent disk data: Target: datafs-OSTffff Index: unassigned Lustre FS: datafs Mount type: ldiskfs Flags: 0x72 (OST needs_index first_time update ) Persistent mount opts: errors=remount-ro,extents,mballoc Parameters: mgsnode=192.168.241.247 at tcp device size = 190734MB formatting backing filesystem ldiskfs on /dev/sda2 target name datafs-OSTffff 4k blocks 0 options -J size=400 -i 16384 -I 256 -q -O dir_index -F mkfs_cmd = mkfs.ext2 -j -b 4096 -L datafs-OSTffff...

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here:

Hello, I''ve several problems with quota on our testcluster: When I set the quota for a person to a given value (e.g. the values which are provided in the operations manual), I''m able to write exact the amount which is set with setquota. But when I delete the files(file) I''m not able to use this space again. Here is what I''ve done in detail: lfs checkquota