search for: fsstress

Chris: I''m consistently getting oopses when running fsstress against both single and multiple device compressed btrfs filesystems using kernels built from the current btrfs-unstable. In this report, I''m describing an incident with a single device filesystem. Once the oops occurs, all I/O appears to stop though iowait is still reported, and fss...

Hi, I am getting an I/O error while running fsstress on client samba mount point (only with smbfs) Can anyone, please look into this problem? Problem Description: x370 was configured for samba server & x206f as samba client. fsstress was running from two samba mount points from client i.e /SAMBA1 (type cifs) & /SAMBA2 (type smbfs). There...

Does samba server handle multiple smb commands (not necessarily andx commands) within one packet? If a client were to send commands such as 0x2f, 0x32, 0x32 in one packet instead of three separate packets, does samba server handle it i.e. respond to each of the three requests?

Hi. I''ve almost all file system functions working. I started to run some heavy file system regression tests. They work. fsx wasn''t able to break my port, but the test you can find here: http://people.freebsd.org/~kan/fsstress.tar.gz broke it. My kernel panics on this assertion (zfs_dir.c): 749: mutex_exit(&dzp->z_lock); 750: 751: error = zap_remove(zp->z_zfsvfs->z_os, dzp->z_id, dl->dl_name, tx); 752-> ASSERT(error == 0); 753: 754: if (reaped_ptr != NULL) zap_remove() returns ENOENT, which is re...

...] [<ffffffff8104da7c>] kthread+0xba/0xc2 [ 413.409157] [<ffffffff8104d9c2>] ? kthread_freezable_should_stop+0x52/0x52 [ 413.409157] [<ffffffff8161fd1c>] ret_from_fork+0x7c/0xb0 [ 413.409157] [<ffffffff8104d9c2>] ? kthread_freezable_should_stop+0x52/0x52 [ 413.409157] fsstress D ffff88007827c308 0 4730 4729 0x00000000 [ 413.409157] ffff88007717fd58 0000000000000082 ffff88007717fe18 ffff88007717ffd8 [ 413.409157] 0000000000004000 0000000000012c80 ffffffff81c11410 ffff88007caf2fb0 [ 413.409157] ffff88007717fca8 ffffffff8111bb58 0000000000000000 ffff8800...

This reverts commit 5500cdbe14d7435e04f66ff3cfb8ecd8b8e44ebf. We had numerous reports of premature ENOSPC that were bisected to this patch. Reverting will not break things but a warning in ''use_block_rsv'' may show up in the syslog. There''s no alternative fix in sight and the ENOSPC problem affects all 3.3 btrfs users during normal filesystem use. CC:

Hi. I''m all set for doing performance comparsion between Solaris/ZFS and FreeBSD/ZFS. I spend last few weeks on FreeBSD/ZFS optimizations and I think I''m ready. The machine is 1xQuad-core DELL PowerEdge 1950, 2GB RAM, 15 x 74GB-FC-10K accesses via 2x2Gbit FC links. Unfortunately the links to disks are the bottleneck, so I''m going to use not more than 4 disks, probably.