[ANN] unionfs patchset-17 release, lock mechanism changed for robust working

Hi Guys!

It is my pleasure and honor to announce the availability of
the unionfs patchset-17. p17 have some significant improvements
around the lock mechanism for robust and stable working.

Patchset-17:
   For 7-current
     http://people.freebsd.org/~daichi/unionfs/unionfs-p17.diff

   For 6.x
     sorry, it is for current only.

   Changes in unionfs-p17.diff
     - Fs takes illegal access without lock of lower layer
       vnode if the both upper/lower layers have both vnode.
       To fix this problem, we change the lock mechanism to
       get locks for both upper/lower layer always.
     - Kernel gets a dead-lock easily within above
       upper/lower-layer-always-lock-mechanism. To avoide
       above dead-lock, we changed vfs_lookup.c. By that change,
       it always locks vnodes parent first and children second.
       You could see the same lock-order-control implementation
       around cache_lookup.
     - It takes the both open/close operations per kernel thread.
     - It takes readdir-treat-status-management per kernel thread.
     - It reopens vnode if needed when coping to upper layer on
       advlock.
     - mount_unionfs(8) changes option style fitting for fstab(5)
       style. (by rodrigc)

ACL broken on all FreeBSD variants

Hey!

Just choosed that provocant topic, because there seem to be no
reaction on all the reports I send about FreeBSD ACLs.

Just wanted to know, whether anyone REALLY uses ACLs with
default entries. If so, does it really work with creating
new files?

All my tests say no, and I testet 5.4, 6.1, 6.2.

If someone could confirm that FreeBSD does have ongoing and
unfixed ACLs this would help me, so I can stop spending time on tests.

Sincerly

Nico

P.S.: 
I reported on freebsd-questions problems with Default ACLs
on 2006-10-18, <20061018141753.GA12559 <at> schottelius.org>.

I reported on freebsd-fs problems with Default ACLs
on 2006-11-23, <20061123171444.GG24205 <at> schottelius.org>.

--

-- 
``...if there's one thing about Linux users, they're do-ers, not whiners.''
(A quotation of Andy Patrizio I completely agree with)

Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working

Hi guys, it's congratulations!

It is a red-letter day for new FreeBSD unionfs. The unionfs-17.diff
(without patch for sys/kern/vfs_lookup.c) was  committed to FreeBSD
7-current of 2006-12-02 19:35:56 UTC by rodrigc, my src mentor.

>   Current English document of web has some Japanese contents. We
> need a translator 

Hiroharu TAMARU-san gave us good English text. Thanks.
And we added some text around committed of current.

    http://people.freebsd.org/~daichi/unionfs/  (English)
    http://people.freebsd.org/~daichi/unionfs/index-ja.html  (Japanese)

Hopefully we can get more feedback from testers :)

--

-- 
  Daichi GOTO, http://people.freebsd.org/~daichi
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"

Re: Snap Server filesystem?

Eric Anderson wrote:
> On 11/22/06 23:37, David Horis wrote:
>> Hello All,
>>
>> Note: This was originally posted to the freebsd-questions list...
>>
>> A Snap Server 1100 just died on me... (Single drive, FreeBSD-based, I 
>> think...)
>>
>> I think it's not HD related as I can't even get into to the 
>> hardware/bios reset mode.
>>
>> I called adaptec, but they were of no help.... No even to tell me 
>> what kind of filesystem is on the drive. They said that since it's an 
>> old product, my only choice is to send the device to an authorized 
>> data recovery firm... ~ 4k USD
>>  
>> Have you folks ever heard of anyone opening one of these things up 
>> and mounting the drive on a regular PC?
>>
>> Since the drive probably has some coruption, due to the MB/OS crash, 
>> how would I go about fixing those before I mount the drive and try to 
>> copy off the files?
>>
>> I've tried accessing the drive via Knoppix and the GpartEd LiveCD... 
>> both see the disk, but report it to empty of partitions.
>>
>> I am unfamiliar with *nix, and am unsure what to try next.  If 
>> someone could provide guidance on this, it would be greatly 
>> appreciated.  :)

ZFS patches for FreeBSD.

Hi Pawel

Iam trying to build zfs for freebsd. It builds fine and it runs and  
all that.
But I still have this kmem panic. I know you said to ignore that  
because you
know it already. But I thought you maybe fixed it in change 110386 in  
p4.

So what is the actual state of this kmem panic?

Denis

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"

FreeBSD-7.0 on ZFS

Kind time of day. I had a problem of loading of the module....

BSDsystem# kldload zfs.ko
kldload: can't load zfs.ko: No such file or directory
BSDsystem# locate zfs.ko
/boot/kernel/zfs.ko
/boot/kernel/zfs.ko.symbols
/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zfs/zfs.ko
/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zfs/zfs.ko.debug
/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zfs/zfs.ko.symbols
BSDsystem# kldload /boot/kernel/zfs.ko
kldload: can't load /boot/kernel/zfs.ko: No such file or directory
BSDsystem# ls -al /boot/kernel/zfs.ko
-r-xr-xr-x 1 root wheel 577771 Dec 8 12:15 /boot/kernel/zfs.ko

All pregoing operations are executed consistently and without erroneous.

___
Thankful in advance.
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"

Re: FreeBSD-7.0 on ZFS

On Tue, Dec 12, 2006 at 03:29:07PM +1000, basteon wrote:
> Kind time of day. I had a problem of loading of the module....
> 
> BSDsystem# kldload zfs.ko
> kldload: can't load zfs.ko: No such file or directory
> BSDsystem# locate zfs.ko
> /boot/kernel/zfs.ko
> /boot/kernel/zfs.ko.symbols
> /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zfs/zfs.ko
> /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zfs/zfs.ko.debug
> /usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/zfs/zfs.ko.symbols
> BSDsystem# kldload /boot/kernel/zfs.ko
> kldload: can't load /boot/kernel/zfs.ko: No such file or directory
> BSDsystem# ls -al /boot/kernel/zfs.ko
> -r-xr-xr-x 1 root wheel 577771 Dec 8 12:15 /boot/kernel/zfs.ko
> 
> 
> All pregoing operations are executed consistently and without erroneous.

Review the console log, it probably failed to load because of missing
symbols.  Make sure your kernel + module were both built with -O (not
-O2).  You may need to also enable some of the -D options depending on
what is in your kernel.

Kris

Re: FreeBSD-7.0 on ZFS

On Tue, 12 Dec 2006 00:39:18 -0500
Kris Kennaway <kris <at> obsecurity.org> wrote:
> Review the console log, it probably failed to load because of missing
> symbols.  Make sure your kernel + module were both built with -O (not
> -O2).  You may need to also enable some of the -D options depending on
> what is in your kernel.

	I have a patch to fix this issue, and I'm testing ZFS.

--- sys/modules/zfs/Makefile.orig	Tue Dec 12 23:16:12 2006
+++ sys/modules/zfs/Makefile	Mon Dec 11 13:12:06 2006
 <at>  <at>  -42,6 +42,9  <at>  <at> 
 SRCS+=	subr_kernio.c
 SRCS+=	vdev_geom.c

+.PATH:	${.CURDIR}/../../libkern
+SRCS+=	memset.c
+
 CWARNFLAGS=-Wall
 CWARNFLAGS+=-Wno-unknown-pragmas
 CWARNFLAGS+=-Wno-missing-braces
--- /dev/null	Tue Dec 12 23:11:00 2006
+++ sys/libkern/memset.c	Mon Dec 11 13:12:44 2006
 <at>  <at>  -0,0 +1,45  <at>  <at> 
+/*-
+ * Copyright (c) 1988, 1993
+ *	The Regents of the University of California.  All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions

Re: ZFS patches for FreeBSD.

On Sun, Dec 10, 2006 at 02:19:57PM +0100, Denis Ahrens wrote:
> Hi Pawel
> 
> Iam trying to build zfs for freebsd. It builds fine and it runs and all that.
> But I still have this kmem panic. I know you said to ignore that because you
> know it already. But I thought you maybe fixed it in change 110386 in p4.
> 
> So what is the actual state of this kmem panic?

Unfortunately it's still not fixed...

--

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd <at> FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!

Re: expectatio

might express it better. My degrees are in archeology and cultural

Re: expectatio 
Of course. As soon as your false credentials were filed the
Our gold-clad greeter bowed to us, then led the way. Towards the brick
Fascinated, we all leaned forward to look. Yes, there was the recess.
the wrists, crossed my arms with a single spasmodic burst of effort
flock coming up.
walking around here. But before you answer that-who do you think the
these dreadful compositions yet another time. He plugged in the cubes
equally well as I slipped away between the interstices of society.
We followed the flapping black nylon tail through the streets and

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"