Displaying 4 results from an estimated 4 matches for "lk_exclusive".
Did you mean:
_exclusive
1999 Sep 03
0
FreeBSD-SA-99:01: BSD File Flags and Programming Techniques
...e as root.
+ */
+ if ((vp->v_type == VCHR || vp->v_type == VBLK) &&
+ ((error = suser_xxx(p->p_ucred, p, PRISON_ROOT)) != 0))
+ return (error);
+
VOP_LEASE(vp, p, p->p_ucred, LEASE_WRITE);
vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p);
VATTR_NULL(&vattr);
vattr.va_flags = flags;
error = VOP_SETATTR(vp, &vattr, p->p_ucred, p);
VOP_UNLOCK(vp, 0, p);
- return error;
+ return (error);
}
/*
FreeBSD-3.2-sta...
2006 Apr 23
1
fsck_ufs locked in snaplk
Colleagues,
one of my servers had to be rebooted uncleanly and then I have backgrounded
fsck locked for more than an our in snaplk:
742 root 1 -4 4 1320K 688K snaplk 0:02 0.00% fsck_ufs
File system in question is 200G gmirror on SATA. Usually making a snapshot
(e.g., for making dumps) consumes 3-4 minutes for that fs, so it seems to me
that filesystem is in a deadlock.
Any
2012 Sep 30
2
rsync over NFSv4
Hi,
my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site
9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01
CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC
i386) crashes reproducibly when rsync-ing files to an NFSv4 share on
the FreeBSD machine. The crash makes the system reboot. The crash
creates files in /var/crash which may be obtained
2013 Jul 07
1
Shutdown hangs on unmount of a gjournaled file system in 8-Stable
The problem occurs after an update of 8-stable from r248120 to r252111.
Sometimes shutdown hangs:
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 done
All buffers synced.
>From the kernel