similar to: Need help making lsof work with ZFS

Hi, Since almost all operations in the FUSE low-level API identify files by inode number, I''ve been using zfs_zget() to get the corresponding znode/vnode in order to call the corresponding VFS function in zfs_vnops.c. However, there are some cases when zfs_zget() behaves slightly different than I need: 1) If zp->z_unlinked != 0 then zfs_zget() returns ENOENT. I need it to return

Hello, I'm experiencing a kernel panic that appears to be caused by zfs. No errors are making it into /var/log/messages, but here is the error message that appears on my screen after panic (transcribed): panic solaris assert BSWAP_32(sa_hdr_phys->sa_magic) == SA_MAGIC, file: /src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c, line 1262 I can reproduce this by

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 =

In zfs_mount() function, when we process a mount by a regular user through the delegated administration, the comment states: /* * Make sure user is the owner of the mount point * or has sufficient privileges. */ This makes sense, but the code doesn''t match the comment. The code ensures that user is the owner of the mount point _and_ can write to the directory. Or does "has

Hi folks, Myself and a colleague are currently involved in a prototyping exercise to evaluate ZFS against our current filesystem. We are looking at the best way to arrange the disks in a 3510 storage array. We have been testing with the 12 disks on the 3510 exported as "nraid" logical devices. We then configured a single ZFS pool on top of this, using two raid-z arrays. We are getting

Hi all, You will find in attachment to this mail some benchmarks we made on Linux with pios over ZFS-DMU. There are some interesting things about ZFS tuning and some ideas for breaking a bottleneck we identified in DMU. Thomas LEIBOVICI CEA/DAM - Ile de France -------------- next part -------------- A non-text attachment was scrubbed... Name: ZFS_benchs_Linux.pdf Type: application/pdf Size:

Does ZFS support any type of remote mirroring? It seems at present my only two options to achieve this would be Sun Cluster or Availability Suite. I thought that this functionality was in the works, but I haven''t heard anything lately. Thanks! Aaron Newcomb http://opennewsshow.org http://thesourceshow.org This message posted from opensolaris.org

I''m observing the following behavior in our environment (Sol10U2, E2900, 24x96, 2x2Gbps, ...) - I''ve a compressed ZFS filesystem where I''m creating a large tar file. I notice that the tar process is running fine (accumulating CPU, truss shows writes, ...) but for whatever reason the timestamp on the file doesn''t change nor does the file size change. The same is

We have finished a beta version of the feature. A webrev for it can be found here: http://cr.illumos.org/~webrev/sensille/fits-send/ It adds a command ''zfs fits-send''. The resulting streams can currently only be received on btrfs, but more receivers will follow. It would be great if anyone interested could give it some testing and/or review. If there are no objections,

Hi, When using lsof, I see that smbd changes ownership from the actual user who made the connection, to root. Also seeing odd behavior with certain files accessed from XP boxes suddenly becoming "read only" to the user mid edit, and appears to be related. Ex: lsof output at 8:45 AM: smbd 11987 user1 cwd DIR 253,3 4096 704687 /home/Shares/Groups within a

From: Ralph Angenendt <ra+centos at br-online.de> > If you can read binary :) > The script section of the glibc RPM is a very simple one: > [angenenr at shutdown dict]$rpm -q --scripts glibc > postinstall program: /usr/sbin/glibc_post_upgrade.i686 > postuninstall program: /sbin/ldconfig > And I cannot find Documentation for glibc_post_upgrade at the moment, a >

CentOS Errata and Bugfix Advisory 2012:0442 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0442.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 73447eac806b56cfc12c1b2630e5c9e730711d4b6ffd442c485027055039354b lsof-4.82-4.el6.i686.rpm x86_64:

On Thursday 23 July 2015 16:24:23 Richard W.M. Jones wrote: > Useful for debugging unmount failures. Note that we include lsof in > the appliance already. > --- > daemon/mount.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/daemon/mount.c b/daemon/mount.c > index c5b7d89..e139482 100644 > --- a/daemon/mount.c > +++ b/daemon/mount.c > @@ -424,6

I did something simple; on one window did more/etc/mail/sendmail.cf on another window did lsof -o -b -p XXX -w where XXX is the process number. The SIZE column does not change to OFFSET! the size reflects the size of sendmail.cf - I was hoping the "-o" would change the SIZE column to OFFSET column and show at what offset the program has read into the file? AM I doing something wrong?

Hi, I noticed this today. If I build lsof on my 4-STABLE box, then it doesn't run: boojum# lsof lsof: PID 0, no file * space If I build the lsof binary under 4.8-STABLE, then it runs fine under 4.8-STABLE and 4-STABLE. Upon investigation it appears that the variable fd in the file dproc.c is being used uninitialized in gather_proc_info(). The problem seems to be related to some changes to

Useful for debugging unmount failures. Note that we include lsof in the appliance already. --- daemon/mount.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/daemon/mount.c b/daemon/mount.c index c5b7d89..e139482 100644 --- a/daemon/mount.c +++ b/daemon/mount.c @@ -424,6 +424,10 @@ do_umount_all (void) r = command (NULL, &err, str_umount, mounts.argv[i], NULL); if (r == -1)

On Thu, Jul 23, 2015 at 05:29:43PM +0200, Pino Toscano wrote: > On Thursday 23 July 2015 16:24:23 Richard W.M. Jones wrote: > > Useful for debugging unmount failures. Note that we include lsof in > > the appliance already. > > --- > > daemon/mount.c | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/daemon/mount.c b/daemon/mount.c

From: Simon Perreault <nomis80 at lqt.ca> > Sure, theoretically it would be possible, but how would you restart this one? > [nomis80 at poste10-153 ~]$ sudo lsof | grep libc | grep init > init 1 root mem REG 253,0 1521500 999437 /lib/tls/libc-2.3.5.so I need to verify the post-install script for the glibc RPM, but I believe it SIGHUPs the process -- and

hi, lsof on freebsd 9.1: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ntpd 1707 root cwd unknown file system type: newnfs ntpd 1707 root rtd unknown file system type: newnfs ntpd 1707 root txt unknown file system type: newnfs ntpd 1707

In another thread recursive snapshot creation was found atomic so that it is done quickly, and more important, all at once or nothing at all. Do you know if recursive destroying and renaming of snapshots are atomic too? Regards Henrik Heino