search for: iopen_nopriv

In 1.6.0, when creating a MDT, you could specify multiple --mgsnode options and it would failover between them. 1.6.3 only seems to take the last one and --mgsnode=192.168.1.252 at o2ib:192.168.1.253 at o2ib doesn''t seem to failover to the other node. Any ideas how to get around this? Robert Robert LeBlanc College of Life Sciences Computer Support Brigham Young University leblanc at

Hi, Our lustre environment is: 2.6.9-55.0.9.EL_lustre.1.6.3smp I would like to change recovery timeout from default value 250s to something longer I tried example from manual: set_timeout <secs> Sets the timeout (obd_timeout) for a server to wait before failing recovery. We performed that experiment on our test lustre installation with one OST. storage02 is our OSS [root at

...provements to the inode and block allocators by Andrew Morton * The bugfix for noatime on newly created inodes * An open by inode number extension (this was an old patch I developed a while ago, updated for the latest 2.4 kernels; nothing changes unless a filesystmem is mounted with the iopen or iopen_nopriv mount options; see Documentation/filesystems/ext2.txt for more information) Also included in this patchset (over stock 2.4.21rc5) are: * dxdir/htree support for fast directory lookups * honor default mount options stored in the ext2/3 superblock. * forward compatibility: dynamic resizing * fo...

.../sda1 WARNING: MDS group upcall is not set, use ''NONE'' Permanent disk data: Target: datafs-MDTffff Index: unassigned Lustre FS: datafs Mount type: ldiskfs Flags: 0x75 (MDT MGS needs_index first_time update ) Persistent mount opts: errors=remount-ro,iopen_nopriv,user_xattr Parameters: device size = 95367MB formatting backing filesystem ldiskfs on /dev/sda1 target name datafs-MDTffff 4k blocks 0 options -J size=400 -i 4096 -I 512 -q -O dir_index -F mkfs_cmd = mkfs.ext2 -j -b 4096 -L datafs-MDTffff -J size=400 -i 4096 -I...

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