From owner-freebsd-fs@FreeBSD.ORG Sun Jul 22 06:29:03 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3BAD0106566B for ; Sun, 22 Jul 2012 06:29:03 +0000 (UTC) (envelope-from mehdi.esmaeelpour@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 050C48FC14 for ; Sun, 22 Jul 2012 06:29:02 +0000 (UTC) Received: by obbun3 with SMTP id un3so9727884obb.13 for ; Sat, 21 Jul 2012 23:29:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Bk8VclRkrnRuS+VWePrr62136OE4ELPuYxOGmwC0A1A=; b=ZtngO+Q17PzNmqe3d0C+zQiaSAaKBsciactN0q45K+pJMbFjCSSoYwkwLeGTFOq9Jh NN5tdglx0+a8NnkmhqM5TKCalIxheeY55WzHITEdsRxWyrQ8+rbfOXQ/bTwwe8ADPOfa LJfWySjHIbiUoA+wewG7LwbE2km8wV9Tu6rEQaMVbJcET4Xiawh50HPUpXSB2UwNpg4x urG8g+BegSZMHb0GCOGMAqgw8qPIWv3HV2ovtdke9p0HBHpDvuHQTiHzpNOI3x2FSHr1 Z4GZjeLVb6O5gI0elcXipFg+c9KNHIRIBCANSuTnuuPITsSspZSrlWXrUx4cqhfAcHdh Y3Nw== MIME-Version: 1.0 Received: by 10.50.193.196 with SMTP id hq4mr11689048igc.57.1342938542404; Sat, 21 Jul 2012 23:29:02 -0700 (PDT) Received: by 10.64.100.231 with HTTP; Sat, 21 Jul 2012 23:29:02 -0700 (PDT) Date: Sun, 22 Jul 2012 10:59:02 +0430 Message-ID: From: Mehdi Esmaeelpour To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: vnode X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 06:29:03 -0000 folks How i use vn_rdwr() to write to a file? i am starter and don't know anything! but i search for this but cannot find anything. Thanks From owner-freebsd-fs@FreeBSD.ORG Sun Jul 22 06:32:45 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C3AC106566B for ; Sun, 22 Jul 2012 06:32:45 +0000 (UTC) (envelope-from rafi@ugcs.caltech.edu) Received: from fox.seas.upenn.edu (foxv6.seas.upenn.edu [IPv6:2607:f470:8:64:5ea5::e]) by mx1.freebsd.org (Postfix) with ESMTP id C6B848FC0A for ; Sun, 22 Jul 2012 06:32:44 +0000 (UTC) Received: from [192.168.1.83] (pool-173-49-61-41.phlapa.fios.verizon.net [173.49.61.41]) (authenticated bits=0) by fox.seas.upenn.edu (8.14.5/8.14.3) with ESMTP id q6M6WeGs005281 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 22 Jul 2012 02:32:40 -0400 Message-ID: <500B9E83.6030509@ugcs.caltech.edu> Date: Sun, 22 Jul 2012 02:32:35 -0400 From: Rafi Rubin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4 MIME-Version: 1.0 To: Peter Maloney References: <500A9787.5060109@ugcs.caltech.edu> <500AC46D.309@brockmann-consult.de> In-Reply-To: <500AC46D.309@brockmann-consult.de> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-07-21_05:2012-07-20, 2012-07-21, 1970-01-01 signatures=0 X-PP-Spam-Details: rule=add_spam_details policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1207210422 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS deadlock X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 06:32:45 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'll have to read those more carefully later. From what I've read so far, it looks like that happens with a single nfs client. In my case, a single client isn't a problem, and when I drop the nfsd to a single thread, many clients (of course in reality just one at a time), are safe. I have no problem reading the .zfs directory and my snapshots. I'm also not sure if the .zfs dir is actually more sensitive than anything else. I was just happy to find something that triggered this bug reliably. I plan to explore more after I setup a non-production machine for testing. We've been seeing crashes on the order of once every 2-7 days. And I doubt anyone has been using the .zfs directories (but I'm can't be sure). Also, the failure mode isn't quite the same (crashing or rebooting the server instead of just freezing one volume), but I've been changing things around to try to bisect the problem. This is just the first consistent bug that I've been able to identify. Rafi On 07/21/12 11:02, Peter Maloney wrote: > I've had the same thing happen. It only happens with Linux clients. My > workaround is to mount an empty directory on top of .zfs. I submitted a PR > about it also. And I can't reproduce it on other machines, including the > replicated backup server with all the same snapshots. It only happens on > the one production machine, possibly because it has more nfs clients > active than what I created for my tests. > > Here's my forum thread: http://forums.freebsd.org/showthread.php?t=29648 > > Here's my PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/168947 > > > On 07/21/2012 01:50 PM, Rafi Rubin wrote: >> I have a small server with a mirrored pair of hard drives that handles >> generally light loads for a number of linux machines over nfs v3. >> >> I've been seeing some deadlocks (and possibly worse) lately. I've >> narrowed down the freezing to a simple test run simultaneously on a >> number of the client machines: >> >> mount host:/food/bar ls bar/.zfs/snapshot >> >> When I do that, all the client machines hang on any access to the >> server. On the server, only the volume "bar" hangs, the rest are fine. >> >> This occurs even when there is no other load on the server. Also, after >> rebooting the server, the client machines eventually complete the ls and >> behave normally. >> >> >> I think this doesn't happen if the directory is cached, either in memory >> or on an L2 ssd, but I need to rerun some tests. >> >> For now the machine seems to be stable with nfsd limited to a single >> thread. >> >> >> Any help debugging would be appreciated, Rafi >> _______________________________________________ freebsd-fs@freebsd.org >> mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To >> unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > _______________________________________________ freebsd-fs@freebsd.org > mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To > unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQC56AAAoJEPILXytRLnK2C6sP/RtSugG8JXkG50B8U7uiBsPh UPci3oXYh9uP6XALR2Y+41wmem4Hv8BCQylKK2pkdZkU5G4vRn25xE8PTxFTw4st 27EaD8c++Bihg+djP7B+jdfGR4QTIDNpjH1sqk9GZuZ/uppjEjh5GiNjQrnskOEK u3Q6VubBNuHAZ6/QFERsy8ZCYmyWtkQ2g7g99tLDrFDYm48lEabxeE1cuS/Ck6BT IBIqtaujLEWZ8eo8/VG143a5DxMwIjF4FeZ1ingAkiCOFHQu6QEqh7dPfK8CAxg/ sdKS7e3QSi2RKBC5MuV19jQhCXo05QxewfhWtQ4go1yyD9Q733fS7WA9pqtUrLEr DU5mrqJv7U+V68R/I7a0lM+g67H0yoxnYYk6oYfjPfc3o2aSQ+Sa1cfm94BzvOVs 19wGrh1TpKZFWV0DAJqndHLSknPd7Ly6E4r6drLerTABssSXIJxCOJEAjQG8ftzJ ftvxYPydzR0hwff/LEDnNWfd4fLmi++f0zc9mrYAAerrZDAPfT+6FHCASYmU9V6+ HA47UztAsDcTkcM3uOPhgmHQI2FnB5uaBLdK/Z+q96kpSvgsKtWyu/jLlZ/KMjNh xB+hf3OZ8q3q+QoSHDERmd2AXo9ZhTfDLIVfkU10iLaNdxoXhOq8uo5iCX0nzJK2 /sqd8O9CVd91+MfF24X5 =LFIk -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Sun Jul 22 10:01:32 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFB7A10656D6 for ; Sun, 22 Jul 2012 10:01:32 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 73D778FC08 for ; Sun, 22 Jul 2012 10:01:32 +0000 (UTC) Received: by obbun3 with SMTP id un3so10013653obb.13 for ; Sun, 22 Jul 2012 03:01:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xA9cRopD8zK6eU6moWp20t+Dc/dcQLk4lNT3iOtZvLA=; b=OuUyGeub4mrNXpkRHo1iQEX4fChCGPlBAVniOIILr9PBPv4nJ5Juudb/a7qVckONA9 sPGrPA6uOMUpVJnRozooKnfSgMikOB+lH4nFYDfkY7kg6DQoQa+MMwXLY09eNWDur29r 37rlfl0FXIyV+4xl+AWcbPWTQIDd32EwnzeIWWLejdElSYzEY9QkuztlXc6bWfcch0KR yr56dEJCN/97PsCRCCLn4JQfL+JTZDOFschZjZGUWj1iXokvV28g2ZxXaBGC3jogae1g BdlGeWvv10QysuNOhQUc2QVvDRGHEMOV+dc9OI3ZID+OmJdTdQ3YMnQ+ARcyLb1FslSN knfA== MIME-Version: 1.0 Received: by 10.182.88.9 with SMTP id bc9mr15770713obb.4.1342951292089; Sun, 22 Jul 2012 03:01:32 -0700 (PDT) Received: by 10.60.32.81 with HTTP; Sun, 22 Jul 2012 03:01:32 -0700 (PDT) In-Reply-To: <01bf01cd66d4$84756b40$8d6041c0$@com> References: <01bf01cd66d4$84756b40$8d6041c0$@com> Date: Sun, 22 Jul 2012 12:01:32 +0200 Message-ID: From: Andreas Nilsson To: Sam Zehr Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Boot disk read-only? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 10:01:32 -0000 On Sat, Jul 21, 2012 at 2:05 AM, Sam Zehr wrote: > Hello all. > > > > I apologize if this is the wrong place to ask, but I've had good luck with > USB questions in the USB list, so I thought this would be the place. > > > > How do I make a disk in FreeBSD 9.0 _completely_ read-only? > > > > I am converting an embedded system using flash for a disk from BSD 7.0 to > 9.0 > > > > rc.initdiskless is working > > > > I had luck with BSD 7.0 by doing the following additional steps: > > 1. Add noatime to fstab options > > 2. Add vfs.nfs.diskless_valid=1 to /boot/loader.conf > > > > So far this is not working on BSD 9.0. It looks like something is changing > on the disk during boot > > > > The disk is a USB thumb drive > > > > Sysctl vfs.nfs.diskless_valid returns 0 once booted up > > > > Please note that I am not just concerned about files - the entire disk > needs > to be locked, like ROM. > > > > Is there a way to completely lock the disk, even during the boot? > > > > Or perhaps a reason why setting vfs.nfs.diskless_valid=1 in > /boot/loader.conf does not appear to work? > > > > Thanks > > Sam > Perhaps start by reading http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.html which should contain the basics plus some nice extra features. Short version: did you do 'touch /etc/diskless' ? Best regards Andreas From owner-freebsd-fs@FreeBSD.ORG Sun Jul 22 11:25:53 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A96F1065670 for ; Sun, 22 Jul 2012 11:25:53 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-scalar.mail.uoguelph.ca (esa-scalar.mail.uoguelph.ca [66.199.40.18]) by mx1.freebsd.org (Postfix) with ESMTP id 4B3B08FC14 for ; Sun, 22 Jul 2012 11:25:53 +0000 (UTC) Received: from zcs3.mail.uoguelph.ca (new.mail.uoguelph.ca [131.104.93.37]) by esa-scalar.mail.uoguelph.ca (8.14.1/8.14.1) with ESMTP id q6MBAiIb020799; Sun, 22 Jul 2012 07:10:45 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 36F78B4019; Sun, 22 Jul 2012 07:10:43 -0400 (EDT) Date: Sun, 22 Jul 2012 07:10:43 -0400 (EDT) From: Rick Macklem To: Mehdi Esmaeelpour Message-ID: <2086824705.663013.1342955443184.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: vnode X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 11:25:53 -0000 Mehdi Esmaeelpour wrote: > folks > > How i use vn_rdwr() to write to a file? i am starter and don't know > anything! but i search for this but cannot find anything. > I'd say avoid reading/writing files from within the kernel if possible, but if you must do it, you can look at the use of NFSD_RDWR in sys/fs/nfsserver/nfs_nfsdstate.c. (NFSD_RDWR() is just a macro that becomes a call to vn_rdwr(). Look in sys/fs/nfs/nfsport.h for the macro. rick > > Thanks > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Sun Jul 22 15:25:26 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28EAC106564A for ; Sun, 22 Jul 2012 15:25:26 +0000 (UTC) (envelope-from sam@athyriogames.com) Received: from madonna.sslcatacombnetworking.com (madonna.sslcatacombnetworking.com [174.133.19.130]) by mx1.freebsd.org (Postfix) with ESMTP id E5B488FC0C for ; Sun, 22 Jul 2012 15:25:25 +0000 (UTC) Received: from c-98-206-215-156.hsd1.in.comcast.net ([98.206.215.156] helo=laptopv) by madonna.sslcatacombnetworking.com with esmtpa (Exim 4.69) (envelope-from ) id 1Ssxu5-0003EU-Uq; Sun, 22 Jul 2012 10:17:06 -0500 From: "Sam Zehr" To: "'Andreas Nilsson'" References: <01bf01cd66d4$84756b40$8d6041c0$@com> In-Reply-To: Date: Sun, 22 Jul 2012 10:24:58 -0500 Message-ID: <01f601cd681e$297f2b40$7c7d81c0$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac1n79ThjOimdovbTMyGtPbKxV0izQAKc7tA Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - madonna.sslcatacombnetworking.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - athyriogames.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: RE: Boot disk read-only? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 15:25:26 -0000 Thanks Andreas I read the section on NanoBSD, but did not find any reference to 'touch /etc/diskless/ I also had advice to check to see what files are changing: find / -mtime -1d -print Returns changes in /dev, /tmp, and /var only /tmp and /var are memory disks, I assume this is expected behavior. Sam From: Andreas Nilsson [mailto:andrnils@gmail.com] Sent: Sunday, July 22, 2012 5:02 AM On Sat, Jul 21, 2012 at 2:05 AM, Sam Zehr wrote: {edited for brevity} How do I make a disk in FreeBSD 9.0 _completely_ read-only? rc.initdiskless is working 1. Add noatime to fstab options 2. Add vfs.nfs.diskless_valid=1 to /boot/loader.conf So far this is not working on BSD 9.0. It looks like something is changing on the disk during boot Sysctl vfs.nfs.diskless_valid returns 0 once booted up Please note that I am not just concerned about files - the entire disk needs to be locked, like ROM. Or perhaps a reason why setting vfs.nfs.diskless_valid=1 in /boot/loader.conf does not appear to work? Perhaps start by reading http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.html which should contain the basics plus some nice extra features. Short version: did you do 'touch /etc/diskless' ? Best regards Andreas From owner-freebsd-fs@FreeBSD.ORG Sun Jul 22 16:47:04 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 078AB106564A for ; Sun, 22 Jul 2012 16:47:03 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 81B3B8FC1A for ; Sun, 22 Jul 2012 16:47:03 +0000 (UTC) Received: by obbun3 with SMTP id un3so10585856obb.13 for ; Sun, 22 Jul 2012 09:47:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5duMuQFe27oTTGy27eUV8nNsrAfan463TxXl5loDPoY=; b=0QXxCJnfF62ZSS5AvD5VxPhOeqJBg5mrtc/qLj2mKGA1x3frdkulskTXIe3/utORid j88ITrSIwMTb1HvJNkCcy/WjwGXbcM7AHNxeCVwDHBbL//8MGljweLf10VOuOY4kdsbv imFN4dyWK9glYvC1PAMUotoGCc8qSuEW95MQs6JQo+LbFsA3dtPr9Al7od3cpwwImk92 hUigUWo6R8gSM/6LI84iNpcSFlfcjsVuCw2UCsEVwG8w3EpH0/Skhojh+tMzA5qB4t1B egRZZ/rjnE34tf1pyvUU42YS+mpyVWXP/bJUIidaqEfEuFsreJdBDj6dA++RFllA/6pB cGqA== MIME-Version: 1.0 Received: by 10.182.149.105 with SMTP id tz9mr16755814obb.65.1342975622909; Sun, 22 Jul 2012 09:47:02 -0700 (PDT) Received: by 10.60.32.81 with HTTP; Sun, 22 Jul 2012 09:47:02 -0700 (PDT) In-Reply-To: <01f601cd681e$297f2b40$7c7d81c0$@com> References: <01bf01cd66d4$84756b40$8d6041c0$@com> <01f601cd681e$297f2b40$7c7d81c0$@com> Date: Sun, 22 Jul 2012 18:47:02 +0200 Message-ID: From: Andreas Nilsson To: Sam Zehr Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Boot disk read-only? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jul 2012 16:47:04 -0000 You're welcome. In /etc/rc there is: dlv=3D`/sbin/sysctl -n vfs.nfs.diskless_valid 2> /dev/null` if [ ${dlv:=3D0} -ne 0 -o -f /etc/diskless ]; then sh /etc/rc.initdiskless fi Have you tried to add vfs.nfs.diskless_valid to /etc/sysctl.conf? I usually just touch /etc/diskless , works for me ;) man diskless might have some more insights too, if you have not read it. Best regards Andreas On Sun, Jul 22, 2012 at 5:24 PM, Sam Zehr wrote: > Thanks Andreas**** > > ** ** > > I read the section on NanoBSD, but did not find any reference to =91touch > /etc/diskless/**** > > ** ** > > I also had advice to check to see what files are changing:**** > > find / -mtime -1d =96print**** > > ** ** > > Returns changes in /dev, /tmp, and /var only**** > > ** ** > > /tmp and /var are memory disks, I assume this is expected behavior.**** > > ** ** > > Sam**** > > ** ** > > *From:* Andreas Nilsson [mailto:andrnils@gmail.com] > *Sent:* Sunday, July 22, 2012 5:02 AM > > **** > > On Sat, Jul 21, 2012 at 2:05 AM, Sam Zehr wrote:**= * > * > > {edited for brevity}**** > > How do I make a disk in FreeBSD 9.0 _completely_ read-only? > rc.initdiskless is working > > 1. Add noatime to fstab options > 2. Add vfs.nfs.diskless_valid=3D1 to /boot/loader.conf > So far this is not working on BSD 9.0. It looks like something is changin= g > on the disk during boot > Sysctl vfs.nfs.diskless_valid returns 0 once booted up > Please note that I am not just concerned about files - the entire disk > needs > to be locked, like ROM. > Or perhaps a reason why setting vfs.nfs.diskless_valid=3D1 in > /boot/loader.conf does not appear to work? > > **** > > ** ** > > Perhaps start by reading > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/index.html wh= ich > should contain the basics plus some nice extra features.**** > > ** ** > > Short version: did you do 'touch /etc/diskless' ?**** > > ** ** > > Best regards**** > > Andreas**** > From owner-freebsd-fs@FreeBSD.ORG Mon Jul 23 01:07:39 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C0391065670; Mon, 23 Jul 2012 01:07:39 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2EB878FC16; Mon, 23 Jul 2012 01:07:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6N17dUY097875; Mon, 23 Jul 2012 01:07:39 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6N17d9P097871; Mon, 23 Jul 2012 01:07:39 GMT (envelope-from linimon) Date: Mon, 23 Jul 2012 01:07:39 GMT Message-Id: <201207230107.q6N17d9P097871@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/169945: [zfs] [panic] Kernel panic while importing zpool (after having a kernel panic) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 01:07:39 -0000 Old Synopsis: Kernel panic while importing zpool (after having a kernel panic) New Synopsis: [zfs] [panic] Kernel panic while importing zpool (after having a kernel panic) Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 23 01:07:23 UTC 2012 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=169945 From owner-freebsd-fs@FreeBSD.ORG Mon Jul 23 08:30:04 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 475A61065673 for ; Mon, 23 Jul 2012 08:30:04 +0000 (UTC) (envelope-from mehdi.esmaeelpour@gmail.com) Received: from mail-gh0-f182.google.com (mail-gh0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id E1E898FC0A for ; Mon, 23 Jul 2012 08:30:03 +0000 (UTC) Received: by ghbz22 with SMTP id z22so6065259ghb.13 for ; Mon, 23 Jul 2012 01:30:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NXrogCyuo2I/qEWdmLKGnmpVIn/RINAGhlUO6CZ7cM0=; b=Bpv1R9Oj4JLZTNtG4S6ntkzChHQ9fFtsQ3glxh40JKSRZszAKMHqMLEGgw7ep/xFgY ntJcZHnSe9NPDH6nH8eyKJqY5LW8URPcRZBEmf+Xnw2t0yMWJrysOM/3Tci4NSIpPasI Xv7GruTIFZolrXVW+f4qRutEHrwafjZRolpnUdsEJ3y0ME9wEUM0NidhBqgEQHHzbTWz qfIvCqI3wN9gfyHqCDzXCKajHwNNFP9JqICtPMBbk7dH41OmLLrvPzXcv1Ozt3g23o/J x8a4iPy7NL/wDkV0YSrbI9AQ5YB6vzN6GR9p/b/vGJoH8BH667jbD/Yr3Ru9phwfWhMp ea/g== MIME-Version: 1.0 Received: by 10.50.94.228 with SMTP id df4mr9700097igb.34.1343032202688; Mon, 23 Jul 2012 01:30:02 -0700 (PDT) Received: by 10.64.100.231 with HTTP; Mon, 23 Jul 2012 01:30:02 -0700 (PDT) In-Reply-To: <2086824705.663013.1342955443184.JavaMail.root@erie.cs.uoguelph.ca> References: <2086824705.663013.1342955443184.JavaMail.root@erie.cs.uoguelph.ca> Date: Mon, 23 Jul 2012 13:00:02 +0430 Message-ID: From: Mehdi Esmaeelpour To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: vnode X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 08:30:04 -0000 On Sun, Jul 22, 2012 at 3:40 PM, Rick Macklem wrote: > Mehdi Esmaeelpour wrote: > > folks > > > > How i use vn_rdwr() to write to a file? i am starter and don't know > > anything! but i search for this but cannot find anything. > > > I'd say avoid reading/writing files from within the kernel if possible, > but if you must do it, you can look at the use of NFSD_RDWR in > sys/fs/nfsserver/nfs_nfsdstate.c. (NFSD_RDWR() is just a macro that becomes > a call to vn_rdwr(). Look in sys/fs/nfs/nfsport.h for the macro. > > rick > > > > > Thanks > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > Thanks rick but that file is complex ... and I'm beginner. From owner-freebsd-fs@FreeBSD.ORG Mon Jul 23 11:07:14 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 57ACB1065672 for ; Mon, 23 Jul 2012 11:07:14 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 41ADC8FC08 for ; Mon, 23 Jul 2012 11:07:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6NB7EvC090008 for ; Mon, 23 Jul 2012 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6NB7DAW090006 for freebsd-fs@FreeBSD.org; Mon, 23 Jul 2012 11:07:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Jul 2012 11:07:13 GMT Message-Id: <201207231107.q6NB7DAW090006@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 11:07:14 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/169945 fs [zfs] [panic] Kernel panic while importing zpool (afte o kern/169813 fs [zfs] [patch] Update with Illumos gate issues: 1796, 2 o kern/169480 fs [zfs] ZFS stalls on heavy I/O o kern/169398 fs [zfs] Can't remove file with permanent error o kern/169339 fs panic while " : > /etc/123" o kern/169319 fs [zfs] zfs resilver can't complete o kern/168947 fs [nfs] [zfs] .zfs/snapshot directory is messed up when o kern/168942 fs [nfs] [hang] nfsd hangs after being restarted (not -HU o kern/168158 fs [zfs] incorrect parsing of sharenfs options in zfs (fs o kern/167979 fs [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste o kern/167977 fs [smbfs] mount_smbfs results are differ when utf-8 or U o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene o kern/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167066 fs [zfs] ZVOLs not appearing in /dev/zvol o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165923 fs [nfs] Writing to NFS-backed mmapped files fails if flu o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/162362 fs [snapshots] [panic] ufs with snapshot(s) panics when g o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161897 fs [zfs] [patch] zfs partition probing causing long delay o kern/161864 fs [ufs] removing journaling from UFS partition fails on o bin/161807 fs [patch] add option for explicitly specifying metadata o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic o kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an f bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 282 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jul 23 17:40:25 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C6D30106566C for ; Mon, 23 Jul 2012 17:40:25 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 950DD8FC0C for ; Mon, 23 Jul 2012 17:40:25 +0000 (UTC) Received: from JRE-MBP-2.local (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id q6NHeNY7034195 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 23 Jul 2012 10:40:24 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <500D8C82.2040904@freebsd.org> Date: Mon, 23 Jul 2012 10:40:18 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Mehdi Esmaeelpour References: <2086824705.663013.1342955443184.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: vnode X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 17:40:25 -0000 On 7/23/12 1:30 AM, Mehdi Esmaeelpour wrote: > On Sun, Jul 22, 2012 at 3:40 PM, Rick Macklem wrote: > >> Mehdi Esmaeelpour wrote: >>> folks >>> >>> How i use vn_rdwr() to write to a file? i am starter and don't know >>> anything! but i search for this but cannot find anything. >>> >> I'd say avoid reading/writing files from within the kernel if possible, >> but if you must do it, you can look at the use of NFSD_RDWR in >> sys/fs/nfsserver/nfs_nfsdstate.c. (NFSD_RDWR() is just a macro that becomes >> a call to vn_rdwr(). Look in sys/fs/nfs/nfsport.h for the macro. >> >> rick >> >>> Thanks >>> _______________________________________________ >>> freebsd-fs@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > Thanks rick but that file is complex ... and I'm beginner. there are several parts of the kernel that write out information directly. try looking at the ALQ code. (used with KTR) (ktrdump etc.) > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > From owner-freebsd-fs@FreeBSD.ORG Mon Jul 23 22:20:13 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91517106566B; Mon, 23 Jul 2012 22:20:13 +0000 (UTC) (envelope-from attila.bogar@linguamatics.com) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1.freebsd.org (Postfix) with ESMTP id 4CB078FC17; Mon, 23 Jul 2012 22:20:13 +0000 (UTC) Received: from [10.252.2.234] (vpn11.linguamatics.com [10.252.2.234]) by mail.linguamatics.com (Postfix) with ESMTPSA id 15F19EFB451; Mon, 23 Jul 2012 23:14:41 +0100 (BST) Message-ID: <500DCCD0.8020701@linguamatics.com> Date: Mon, 23 Jul 2012 23:14:40 +0100 From: =?ISO-8859-1?Q?Attila_Bog=E1r?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Matthew Seaman References: <4FF6D7EE.3000806@linguamatics.com> <4FF6DB9A.7040905@FreeBSD.org> In-Reply-To: <4FF6DB9A.7040905@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS: .zfs/snapshot directory vanished X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2012 22:20:13 -0000 Hi Matthew, Just a quick question: Have you been using an L2ARC cache device in the pool where the snapshot dir vanished? Thanks in advance, Attila From owner-freebsd-fs@FreeBSD.ORG Tue Jul 24 00:40:47 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 3A238106567A; Tue, 24 Jul 2012 00:40:47 +0000 (UTC) Date: Tue, 24 Jul 2012 00:40:47 +0000 From: John To: freebsd-fs@freebsd.org Message-ID: <20120724004047.GA62435@FreeBSD.org> References: <7FE7A5F3-53FF-4508-A3D6-562E8FA9764D@nipsi.de> <20120720123255.GA56250@FreeBSD.org> <20120721023537.GB19321@in-addr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120721023537.GB19321@in-addr.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: ISCSI on zvols with two maschines. What needs to be done? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 00:40:47 -0000 ----- Gary Palmer's Original Message ----- > > > ----- dennis berger's Original Message ----- > > >> Hi folks, > > >> > > >> The following question often comes to me, when I speak to my customers. > > >> > > >> Is it possible to attach two systems to the same storage array using shared SAS and use istgt + zfs to provide > > >> a reliable ISCSI target. This could be active/passive or later active/active. In case it's not possible, what needs to be done? > > >> > > >> The questions that came into my mind. > > >> > > >> Can I connect two freebsd to the storage and boot them up? Just that both systems would see the physical devices. > > > > > > Yes, please see: > > > > > > http://people.freebsd.org/~jwd/zfsnfsserver.jpg > > > > This is exactly how I would like to use it. > > --- > > Do I need to zfs import?! > > This is the key bit. What John suggests is that on system A you have > poolA and on system B you have pool B. Both pools have their own, > separate, disks. > > If system A goes down, system B notices this and imports poolA and shares > out its iSCSI devices. > > You have to be careful when system A comes back up that it doesn't > auto-import the pool and negotiates with system B to get it back > > It may be easier to think of a situation where there is only 1 pool. > In this situation, the two servers will be in active/passive mode, > and the passive system will only ever take load if the active node > goes down. > > The important thing to remember is NO filesystem which is included with > FreeBSD by default is cluster aware. This means that two servers > CANNOT both mount filesystems on direct-attached storage without > corrupting the data on the storage. The best you can get active/passive > right now, where only 1 server mounts the filesystem at a time and > the second server takes over in event of failure of the primary server. > > In this instance consider ZFS, even at the zpool layer, to be a > filesystem. Mounting the same zpool from shared storage on two servers > at the same time will almost certainly lead to corruption and probably a > restore from backup tapes. > > Gary What Gary wrote about my comments is correct. Even with ZFS you'll end up in trouble if you zpool import -f on both systems A & B. However, if the OP wanted to do without ZFS or any other file or volume management mechanism, individual drives could be exported by istgt on both systems A & B. Given systems A & B, hooked up with SAS interfaces to the shelves, da0 is the same disk on both A & B, then an instance of istgt could be run on both A & B exporting the same drive. The above leaves all filesystem layer responsibility to the initiator who wants to mount the target (whether single or dual pathed). YMMV, John From owner-freebsd-fs@FreeBSD.ORG Tue Jul 24 05:09:46 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F271106566C for ; Tue, 24 Jul 2012 05:09:45 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 341B38FC0A for ; Tue, 24 Jul 2012 05:09:45 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id q6O59eFE040614 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 24 Jul 2012 06:09:41 +0100 (BST) (envelope-from matthew@FreeBSD.org) X-DKIM: OpenDKIM Filter v2.5.2 smtp.infracaninophile.co.uk q6O59eFE040614 Authentication-Results: smtp.infracaninophile.co.uk/q6O59eFE040614; dkim=none (no signature); dkim-adsp=none Message-ID: <500E2E0C.2040606@FreeBSD.org> Date: Tue, 24 Jul 2012 06:09:32 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Attila_Bog=E1r?= References: <4FF6D7EE.3000806@linguamatics.com> <4FF6DB9A.7040905@FreeBSD.org> <500DCCD0.8020701@linguamatics.com> In-Reply-To: <500DCCD0.8020701@linguamatics.com> X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig00CCB3F9493EC6AFF3FD5406" X-Virus-Scanned: clamav-milter 0.97.5 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS: .zfs/snapshot directory vanished X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 05:09:46 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig00CCB3F9493EC6AFF3FD5406 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 23/07/2012 23:14, Attila Bog=E1r wrote: > Just a quick question: > Have you been using an L2ARC cache device in the pool where the snapsho= t > dir vanished? No, nothing like that. It's just a pair of SATA drives: lucid-nonsense:~:% zpool status xroot pool: xroot state: ONLINE scan: resilvered 64.7G in 0h31m with 0 errors on Fri Jun 22 19:08:17 20= 12 config: NAME STATE READ WRITE CKSUM xroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 ada1p3 ONLINE 0 0 0 errors: No known data errors Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --------------enig00CCB3F9493EC6AFF3FD5406 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAOLhQACgkQ8Mjk52CukIznBACeOYGpeLmDy1mZO5WHfXS42iAz bikAnjwuqHHrrnDtZMGB5Xx7cIC4Tzu2 =Ghjr -----END PGP SIGNATURE----- --------------enig00CCB3F9493EC6AFF3FD5406-- From owner-freebsd-fs@FreeBSD.ORG Tue Jul 24 11:17:46 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4296106566B; Tue, 24 Jul 2012 11:17:46 +0000 (UTC) (envelope-from attila.bogar@linguamatics.com) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1.freebsd.org (Postfix) with ESMTP id 6B17F8FC14; Tue, 24 Jul 2012 11:17:46 +0000 (UTC) Received: from secure.linguamatics.com (guardian.linguamatics.com [10.252.2.1]) by mail.linguamatics.com (Postfix) with ESMTPS id 7B7E2EFB460; Tue, 24 Jul 2012 12:17:45 +0100 (BST) Received: from [10.252.2.234] (vpn.abogar.linguamatics.com [10.252.2.234]) by secure.linguamatics.com (Postfix) with ESMTP id 80D978188; Tue, 24 Jul 2012 12:25:08 +0100 (BST) Message-ID: <500E8457.8020805@linguamatics.com> Date: Tue, 24 Jul 2012 12:17:43 +0100 From: =?ISO-8859-1?Q?Attila_Bog=E1r?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Matthew Seaman References: <4FF6D7EE.3000806@linguamatics.com> <4FF6DB9A.7040905@FreeBSD.org> <500DCCD0.8020701@linguamatics.com> <500E2E0C.2040606@FreeBSD.org> In-Reply-To: <500E2E0C.2040606@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS: .zfs/snapshot directory vanished X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 11:17:46 -0000 Hi, Thanks, cache ruled out. I'm trying to isolate the problem. I set up a second box. I wiped 12 disks with dd, created a raidz2 pool, created the datasets and copied all data with rsync (not zfs send to avoid corruption in the zfs stream). All went fine until I turned on I turned on the Amanda backup system. Amanda backs up using creating a snapshot, gtaring the content and then destroying the snapshot. This was issued: # zfs allow -ldu amanda mount,snapshot,destroy tank/export The default port from misc/amanda-server doesn't work bydefault with this feature: define script-tool amzfs_snapshot { comment "backup of zfs snapshot" plugin "amzfs-snapshot" execute-on pre-dle-amcheck, post-dle-amcheck, pre-dle-estimate, post-dle-estimate, pre-dle-backup, post-dle-backup execute-where client } Therefore, I wrote a patch (which I should send to the port maintainer) - it was working fine for a year on 8.2-RELEASE: --- /usr/local/lib/perl5/site_perl/5.14.2/Amanda/Application/Zfs.pm.orig 2012-07-05 11:15:22.000000000 +0100 +++ /usr/local/lib/perl5/site_perl/5.14.2/Amanda/Application/Zfs.pm 2012-07-06 11:28:07.000000000 +0100 @@ -82,9 +82,9 @@ waitpid $pid, 0; close $rdr; close $err; + chomp $zmountpoint; - if ($? == 0) { - chomp $zmountpoint; + if (($? == 0) && (substr($zmountpoint, 0, 1) ne '/')) { # zfs dataset supplied $self->{filesystem} = $device; @@ -377,11 +377,14 @@ my $snapshotname = ""; if ($self->{action} eq 'check') { - $snapshotname = "amanda-" . Amanda::Util::sanitise_filename($self->{disk}) . "-check"; + # $snapshotname = "amanda-" . Amanda::Util::sanitise_filename($self->{disk}) . "-check"; + $snapshotname = "amanda-check"; } elsif (!defined $level) { - $snapshotname = "amanda-" . Amanda::Util::sanitise_filename($self->{disk}) . "-current"; + # $snapshotname = "amanda-" . Amanda::Util::sanitise_filename($self->{disk}) . "-current"; + $snapshotname = "amanda-current"; } else { - $snapshotname = "amanda-" . Amanda::Util::sanitise_filename($self->{disk}) . "-" . $level; + # $snapshotname = "amanda-" . Amanda::Util::sanitise_filename($self->{disk}) . "-" . $level; + $snapshotname = "amanda-" . $level; } return $snapshotname; I kicked off the backup and the snapshots have gone. I also had a kernel panic that it couldn't unmount a snapshot. This is the second box. I have the same problems with 9.1-PRERELEASE. Any help would be greatly appreciated, Thanks, Attila From owner-freebsd-fs@FreeBSD.ORG Tue Jul 24 13:46:31 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 31AEF106566C for ; Tue, 24 Jul 2012 13:46:31 +0000 (UTC) (envelope-from maurizio.vairani@cloverinformatica.it) Received: from smtplq04.aruba.it (smtplq-out5.aruba.it [62.149.158.25]) by mx1.freebsd.org (Postfix) with SMTP id 77CFB8FC14 for ; Tue, 24 Jul 2012 13:46:30 +0000 (UTC) Received: (qmail 26996 invoked by uid 89); 24 Jul 2012 13:46:28 -0000 Received: from unknown (HELO smtp2.aruba.it) (62.149.158.222) by smtplq04.aruba.it with SMTP; 24 Jul 2012 13:46:28 -0000 Received: (qmail 29329 invoked by uid 89); 24 Jul 2012 13:46:28 -0000 Received: from unknown (HELO cloverinformatica.it) (info@cloverinformatica.it@151.55.125.196) by smtp2.ad.aruba.it with SMTP; 24 Jul 2012 13:46:28 -0000 Received: from [192.168.0.185] (ASUS-TERMINATOR [192.168.0.185]) by cloverinformatica.it (Postfix) with ESMTP id 225775E; Tue, 24 Jul 2012 15:46:28 +0200 (CEST) Message-ID: <500EA732.1070401@cloverinformatica.it> Date: Tue, 24 Jul 2012 15:46:26 +0200 From: Maurizio Vairani User-Agent: Mozilla/5.0 (Windows NT 4.0; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Gleb Kurtsou References: <20120621140149.GA59722@reks> In-Reply-To: <20120621140149.GA59722@reks> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: smtp2.ad.aruba.it 1.6.2 0/1000/N X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N Cc: freebsd-fs@freebsd.org Subject: Re: [RFC] tmpfs RB-Tree for directory entries X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 13:46:31 -0000 On 21/06/2012 16.01, Gleb Kurtsou wrote: > Hello, > > Here is patch for CURRENT replacing directory entry linked list with > RB-Tree in tmpfs. Performance improvement varies for different > workloads, it may be negligible for directories with small number of > files or due to VFS name caching. > > http://people.freebsd.org/~gleb/tmpfs-nrbtree.1.patch > > This patch is unrelated to similar changes recently committed to > DragonFly: > https://bugs.dragonflybsd.org/issues/2375 > http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/29ca4fd6da8bb70ae90d8e73ea3c47fda22491a7 > > My patch uses name hashes instead of comparing entries by file name, > moreover it reuses the same hash value as directory entry offset and > eliminates possible issue of duplicate directory offsets on 64-bit > archs. In other words it makes VOP_READDIR on large directories faster > for non-zero offsets. > > I'm willing to commit the patch and would appreciate if people actively > using tmpfs give it a try. > > Thanks, > Gleb. > > > ** file_create test from DragonFly PR > % time ~/file_create 10000 > > x tmpfs-file_create-rb > + tmpfs-file_create-orig > +------------------------------------------------------------------------+ > | + | > |x + | > |xx + | > |xx + +| > |A| | > | |MA_| | > +------------------------------------------------------------------------+ > N Min Max Median Avg Stddev > x 5 0.112 0.14 0.119 0.1234 0.012116105 > + 5 2.551 2.734 2.551 2.5886 0.081309901 > Difference at 95.0% confidence > 2.4652 +/- 0.0847787 > 1997.73% +/- 68.7023% > (Student's t, pooled s = 0.0581296) > > > ** test1 -- create 5000 files, rename some of them, remove files > time sh ~/test1.sh > > x tmpfs-test1-rb > + tmpfs-test1-orig > +------------------------------------------------------------------------+ > | x x x + +++ | > ||___MA_____| | > | |_____________A______M______|| > +------------------------------------------------------------------------+ > N Min Max Median Avg Stddev > x 4 5.893 6.091 5.932 5.9535 0.093289871 > + 4 6.49 7.006 6.987 6.8655 0.25058931 > Difference at 95.0% confidence > 0.912 +/- 0.327153 > 15.3187% +/- 5.49514% > (Student's t, pooled s = 0.189074) > > > test1.sh: > #!/bin/sh > for i in `jot 5000`; do echo $i> longername$i; done > ls>/dev/null > for i in `jot 899 100`; do mv longername$i longername1$i; done > ls>/dev/null > for i in `jot 899 100`; do mv longername2$i longername3$i; done > ls>/dev/null > for i in `jot 5000`; do rm longername$i 2>/dev/null; done > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to"freebsd-fs-unsubscribe@freebsd.org" I applied patch on my test machines on 9-STABLE with 4G RAM and 2G of swap space : # uname -a FreeBSD clover-nas-test 9.0-STABLE FreeBSD 9.0-STABLE #2: Tue Jul 10 17:45:25 CEST 2012 ssh@clover-nas-test:/usr/obj/usr/src/sys/GENERIC amd64 # swapinfo -h Device 1K-blocks Used Avail Capacity /dev/zvol/poolusb/swap 2097152 3.5M 2G 0% tmpfs is used for : # df -h | grep tmpfs tmpfs 2.2G 1.1M 2.2G 0% /tmp tmpfs 2.2G 4.0k 2.2G 0% /var/tmp tmpfs 2.2G 188k 2.2G 0% /var/log tmpfs 2.2G 120k 2.2G 0% /var/run tmpfs 2.2G 36k 2.2G 0% /var/db/entropy tmpfs 2.2G 512k 2.2G 0% /var/db/samba tmpfs 2.2G 32k 2.2G 0% /var/spool No regression for three days even low memory condition. # dmesg | grep swap pid 58480 (ssh), uid 0, was killed: out of swap space From owner-freebsd-fs@FreeBSD.ORG Tue Jul 24 16:06:29 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CE02106564A for ; Tue, 24 Jul 2012 16:06:29 +0000 (UTC) (envelope-from sam@athyriogames.com) Received: from madonna.sslcatacombnetworking.com (madonna.sslcatacombnetworking.com [174.133.19.130]) by mx1.freebsd.org (Postfix) with ESMTP id 544DF8FC16 for ; Tue, 24 Jul 2012 16:06:29 +0000 (UTC) Received: from c-98-206-215-156.hsd1.in.comcast.net ([98.206.215.156] helo=laptopv) by madonna.sslcatacombnetworking.com with esmtpa (Exim 4.69) (envelope-from ) id 1SthUr-0004eT-Gh for freebsd-fs@freebsd.org; Tue, 24 Jul 2012 10:58:05 -0500 From: "Sam Zehr" To: References: <01bf01cd66d4$84756b40$8d6041c0$@com> In-Reply-To: Date: Tue, 24 Jul 2012 11:06:13 -0500 Message-ID: <02b201cd69b6$413ea000$c3bbe000$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac1n79ThjOimdovbTMyGtPbKxV0izQBxNvHA Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - madonna.sslcatacombnetworking.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - athyriogames.com Subject: Make disk completely read-only? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 16:06:29 -0000 Hi, this is Sam again, working on making a USB flash drive in FreeBSD 9.0 _completely_ read-only. Disk is mounted read-only - fstab has ro,noatime Following some advice from the list, I've done some binary compares to see what is going on. It looks like only a few bytes are changing every time I reboot, they seem to correspond with the superblock locations - I would guess a timestamp of mount time? I executed the dumpfs command after a few boots, and checked for differences. The only thing that is changing is from the first line Pass 1: magic 19540119 (UFS2) time Mon Jul 23 11:12:06 2012 superblock location 65536 id [ 4fe363f7 e7fd3a99 ] Pass 2: magic 19540119 (UFS2) time Mon Jul 23 11:28:35 2012 superblock location 65536 id [ 4fe363f7 e7fd3a99 ] Does anyone know of a way to stop this timestamp from occurring? Sam From owner-freebsd-fs@FreeBSD.ORG Tue Jul 24 16:09:17 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 743BF106564A for ; Tue, 24 Jul 2012 16:09:17 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from kazon.borderworlds.dk (kazon.borderworlds.dk [IPv6:2a01:4f8:101:4201::1:1]) by mx1.freebsd.org (Postfix) with ESMTP id 102438FC0A for ; Tue, 24 Jul 2012 16:09:17 +0000 (UTC) Received: from talaxian.borderworlds.dk (localhost [127.0.0.1]) by kazon.borderworlds.dk (Postfix) with ESMTP id ECA025C43 for ; Tue, 24 Jul 2012 18:09:15 +0200 (CEST) Message-ID: <500EC8AB.3050101@borderworlds.dk> Date: Tue, 24 Jul 2012 18:09:15 +0200 From: Christian Laursen Organization: The Border Worlds User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120712 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <01bf01cd66d4$84756b40$8d6041c0$@com> <02b201cd69b6$413ea000$c3bbe000$@com> In-Reply-To: <02b201cd69b6$413ea000$c3bbe000$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Make disk completely read-only? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 16:09:17 -0000 On 07/24/12 18:06, Sam Zehr wrote: > Hi, this is Sam again, working on making a USB flash drive in FreeBSD 9.0 > _completely_ read-only. > > Disk is mounted read-only - fstab has ro,noatime > > Following some advice from the list, I've done some binary compares to see > what is going on. It looks like only a few bytes are changing every time I > reboot, they seem to correspond with the superblock locations - I would > guess a timestamp of mount time? Try adding this line to rc.conf: root_rw_mount="NO" -- Christian Laursen From owner-freebsd-fs@FreeBSD.ORG Tue Jul 24 18:08:19 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F2E81065674 for ; Tue, 24 Jul 2012 18:08:19 +0000 (UTC) (envelope-from ee@athyriogames.com) Received: from madonna.sslcatacombnetworking.com (madonna.sslcatacombnetworking.com [174.133.19.130]) by mx1.freebsd.org (Postfix) with ESMTP id 555B98FC14 for ; Tue, 24 Jul 2012 18:08:19 +0000 (UTC) Received: from c-98-206-215-156.hsd1.in.comcast.net ([98.206.215.156] helo=laptopv) by madonna.sslcatacombnetworking.com with esmtpa (Exim 4.69) (envelope-from ) id 1StjOq-0002JT-GB; Tue, 24 Jul 2012 13:00:00 -0500 From: "Engineering" To: "'Christian Laursen'" , References: <01bf01cd66d4$84756b40$8d6041c0$@com> <02b201cd69b6$413ea000$c3bbe000$@com> <500EC8AB.3050101@borderworlds.dk> In-Reply-To: <500EC8AB.3050101@borderworlds.dk> Date: Tue, 24 Jul 2012 13:08:06 -0500 Message-ID: <02ce01cd69c7$47fbb8e0$d7f32aa0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac1ptbRjYtp+X+aITnifeE2TyN/gbwAETctg Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - madonna.sslcatacombnetworking.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - athyriogames.com Cc: Subject: RE: Make disk completely read-only? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 18:08:19 -0000 On 07/24/12 18:06, Sam Zehr wrote: >> Hi, this is Sam again, working on making a USB flash drive in FreeBSD >> 9.0 _completely_ read-only. >> >> Disk is mounted read-only - fstab has ro,noatime >> >> Following some advice from the list, I've done some binary compares to >> see what is going on. It looks like only a few bytes are changing >> every time I reboot, they seem to correspond with the superblock >> locations - I would guess a timestamp of mount time? >Try adding this line to rc.conf: > >root_rw_mount="NO" Thanks! That does the trick. Sam From owner-freebsd-fs@FreeBSD.ORG Wed Jul 25 13:20:13 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 65024106566C for ; Wed, 25 Jul 2012 13:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 371A78FC12 for ; Wed, 25 Jul 2012 13:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q6PDKCbP027706 for ; Wed, 25 Jul 2012 13:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6PDKCLi027705; Wed, 25 Jul 2012 13:20:12 GMT (envelope-from gnats) Date: Wed, 25 Jul 2012 13:20:12 GMT Message-Id: <201207251320.q6PDKCLi027705@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: u-codabugqsev@aetey.se Cc: Subject: Re: kern/162944: [coda] Coda file system module looks broken in 9.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: u-codabugqsev@aetey.se List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2012 13:20:13 -0000 The following reply was made to PR kern/162944; it has been noted by GNATS. From: u-codabugqsev@aetey.se To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/162944: [coda] Coda file system module looks broken in 9.0 Date: Wed, 25 Jul 2012 15:14:24 +0200 Still no fix? From owner-freebsd-fs@FreeBSD.ORG Wed Jul 25 17:04:40 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3CA1106564A; Wed, 25 Jul 2012 17:04:40 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 46C658FC08; Wed, 25 Jul 2012 17:04:39 +0000 (UTC) Received: by laai10 with SMTP id i10so875626laa.13 for ; Wed, 25 Jul 2012 10:04:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=iIPpTgM53dVsU1XRMgqogbRXi+kPM12x5MGHDpK5wls=; b=cNoBek6XifF1Jo6x1A8OqPv8p5zp8QTTIa4qecUeF/e7jLUD2acOxD4Ycvct/To9mw ll9pSYcKb9JSG4HgZtjk9mCWRN+jgwKyhcsWPS/mENhfm/5+PZrXnPf1Xqr/CzDG5ppt o/gh1gEjnp4+NsnZ9D1l/8jRboBplwSWMtm025AQ7HsZKsVpib82bC9exfYmJsfQZbUs yQyuUDXaH7UrFco/0Zat7v3DoqZjP0hDlJGsxyaqQSLNsPfcYOYPfvOIoXKWe5lYAEkM OW7oXKMc9yWGXSMm2S/1Zex+Cp4eDAdl5U1ekr1SRsMRO4Kj3a2BDytA3yCRS+Cuz+X+ 0dcw== MIME-Version: 1.0 Received: by 10.152.48.6 with SMTP id h6mr26700129lan.30.1343235878178; Wed, 25 Jul 2012 10:04:38 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.112.27.65 with HTTP; Wed, 25 Jul 2012 10:04:37 -0700 (PDT) In-Reply-To: References: <50064FB2.3020409@entel.upc.edu> Date: Wed, 25 Jul 2012 18:04:37 +0100 X-Google-Sender-Auth: W0_UYeMtWfBKbf98-QSoUpMNL40 Message-ID: From: Attilio Rao To: Antony Mawer Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Peter Holm , FreeBSD FS Subject: Re: MPSAFE VFS -- List of upcoming actions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2012 17:04:40 -0000 On 7/21/12, Antony Mawer wrote: > On Wed, Jul 18, 2012 at 6:45 PM, Attilio Rao wrote: >> 2012/7/18, Gustau P=C3=A9rez i Querol : >>> >>> Sorry fo the delay. >>> >>> About the ntfs support, I'd go with fuse and leave the most relevan= t >>> filesystems in kernel space. In fact filesystems not particulary >>> specific and not tied our kernel would go to userspace; thinks like >>> smbfs, nwfs, ntfs, ext2 o ext4 for example should be in userspace (the >>> list is incomplete and I don't really know if all of them are yet >>> implemenent in userspace) in my opinion. That would make them easier to >>> maintain (changes in the kernel would only affect fuse, once fixed all >>> the userspace filesystem would work again). >>> >>> As a bonus, we would get many working fs based on fuse. In the >>> server side gluster is a desirable thing; in the desktop things like >>> gvfs (in the linux world gvfs is used not only by gnome but also by kde >>> or xfce) or truecrypt >> >> I'm really concerned also about ntfs and smbfs at the moment. It seems >> that there is also a FUSE smbfs port, but I never used it and I'm not >> sure about its state at all. > > From what I understand, Apple have done a considerable amount of work > on the FreeBSD-drived smbfs in the latest versions of OS X, based on > the existing smbfs in tree: I've also found that there are 2 FUSE modules for smbfs but pho@ and flo@ still haven't tested them. It may make sense to do so before we commit FUSE to -CURRENT. However, thee is a plan by a $COMPANY to work on the in-kernel version of smbfs and lock it before 10.0 is shipped. In the unlikely events this doesn't happen we will came up with a different plan (assuming we will adopt anyway the FUSE module, if it proves to work well). > http://www.opensource.apple.com/source/smb/smb-552.5/ > > I imagine things like the filesystem locking are probably somewhat > different, but in terms of updating smbfs itself to support newer > features it may be a good base (licensing permitting). smbfs at the > moment lacks in some areas such as DFS support, although I do not know > if the OS X version is any different there (given the consumer focus > of their OS, probably not). There was also a version spun off by > OpenSolaris: > > http://hub.opensolaris.org/bin/view/Project+smbfs/ > > which again was based on the FreeBSD + Apple versions. > > I also have a vested interest in NWFS continuing to work - only from a > legacy point of view where we still interoperate with a number of > Netware 6 servers through this. While those will likely eventually go > away, more than likely before we move to 10.x, if there is anyone > capable of working on it we could supply a test environment. > Unfortunately the actual locking of the NWFS and NCP modules is > outside my sphere of knowledge... If you have NCP, do you think you can try this netncp I never committed because lack of testing?: http://lists.freebsd.org/pipermail/freebsd-fs/2009-January/005617.html IIRC, Apple does a similar thing for netsmb (which suffers from a similar problem as netncp). Do you know if FUSE can support NWFS in any way? Starting providing stress-tests on the current codebase for NWFS/NetNCP (and report bugs found, preparing a list) could be a good way to start the locking effort. Interested developers then can look into such a list and provide necessary insight. Attilio --=20 Peace can only be achieved by understanding - A. Einstein From owner-freebsd-fs@FreeBSD.ORG Wed Jul 25 19:46:41 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BC59106564A; Wed, 25 Jul 2012 19:46:41 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id E4C818FC08; Wed, 25 Jul 2012 19:46:40 +0000 (UTC) Received: by ggnm2 with SMTP id m2so1369831ggn.13 for ; Wed, 25 Jul 2012 12:46:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Wf7PRUOHt/8ame6wHLMaNPcvriEO8/ssoQq6dLt0ko8=; b=Iekdb2Sk1iaLKaBGTqQ94yEeFjwwyQROs3+QaDsc+DmetIc7LObh3t5gjliydBp5+h Go60BRjEidRS7uFiY+ofA7Te5ZeYLQ2KAgsOkPjMQKC9IyuMBnFEelny7aOUjIcJTFIk 0Q7SUUOotnQDd0frqZv9xOIq54yGDWyfE3eOzBFS8NMZ1ApgJ7y9qoDLQQcc/eL4y5AJ Bdm846wLvmSt4M0xlkoBB16mX3w6q9IILRkyQJwX8WeNAitc3Wufm21CPfkCBTRd2Tdw sTM4AgihVx1Z/V7SRdCLDCoD3jo7PcGJPXq75he5oKmdJLb1fE4xG7gWTqbCdrraFkOw 5qug== MIME-Version: 1.0 Received: by 10.60.24.7 with SMTP id q7mr37413149oef.54.1343245600047; Wed, 25 Jul 2012 12:46:40 -0700 (PDT) Received: by 10.76.84.7 with HTTP; Wed, 25 Jul 2012 12:46:39 -0700 (PDT) In-Reply-To: References: <50064FB2.3020409@entel.upc.edu> Date: Wed, 25 Jul 2012 12:46:39 -0700 Message-ID: From: Garrett Cooper To: attilio@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD FS , Peter Holm , freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2012 19:46:41 -0000 On Wed, Jul 25, 2012 at 10:04 AM, Attilio Rao wrote: > On 7/21/12, Antony Mawer wrote: >> On Wed, Jul 18, 2012 at 6:45 PM, Attilio Rao wrote= : >>> 2012/7/18, Gustau P=E9rez i Querol : >>>> >>>> Sorry fo the delay. >>>> >>>> About the ntfs support, I'd go with fuse and leave the most releva= nt >>>> filesystems in kernel space. In fact filesystems not particulary >>>> specific and not tied our kernel would go to userspace; thinks like >>>> smbfs, nwfs, ntfs, ext2 o ext4 for example should be in userspace (the >>>> list is incomplete and I don't really know if all of them are yet >>>> implemenent in userspace) in my opinion. That would make them easier t= o >>>> maintain (changes in the kernel would only affect fuse, once fixed all >>>> the userspace filesystem would work again). >>>> >>>> As a bonus, we would get many working fs based on fuse. In the >>>> server side gluster is a desirable thing; in the desktop things like >>>> gvfs (in the linux world gvfs is used not only by gnome but also by kd= e >>>> or xfce) or truecrypt >>> >>> I'm really concerned also about ntfs and smbfs at the moment. It seems >>> that there is also a FUSE smbfs port, but I never used it and I'm not >>> sure about its state at all. >> >> From what I understand, Apple have done a considerable amount of work >> on the FreeBSD-drived smbfs in the latest versions of OS X, based on >> the existing smbfs in tree: > > I've also found that there are 2 FUSE modules for smbfs but pho@ and > flo@ still haven't tested them. It may make sense to do so before we > commit FUSE to -CURRENT. However, thee is a plan by a $COMPANY to work > on the in-kernel version of smbfs and lock it before 10.0 is shipped. > In the unlikely events this doesn't happen we will came up with a > different plan (assuming we will adopt anyway the FUSE module, if it > proves to work well). > >> http://www.opensource.apple.com/source/smb/smb-552.5/ >> >> I imagine things like the filesystem locking are probably somewhat >> different, but in terms of updating smbfs itself to support newer >> features it may be a good base (licensing permitting). smbfs at the >> moment lacks in some areas such as DFS support, although I do not know >> if the OS X version is any different there (given the consumer focus >> of their OS, probably not). There was also a version spun off by >> OpenSolaris: >> >> http://hub.opensolaris.org/bin/view/Project+smbfs/ >> >> which again was based on the FreeBSD + Apple versions. >> >> I also have a vested interest in NWFS continuing to work - only from a >> legacy point of view where we still interoperate with a number of >> Netware 6 servers through this. While those will likely eventually go >> away, more than likely before we move to 10.x, if there is anyone >> capable of working on it we could supply a test environment. >> Unfortunately the actual locking of the NWFS and NCP modules is >> outside my sphere of knowledge... > > If you have NCP, do you think you can try this netncp I never > committed because lack of testing?: > http://lists.freebsd.org/pipermail/freebsd-fs/2009-January/005617.html > > IIRC, Apple does a similar thing for netsmb (which suffers from a > similar problem as netncp). > Do you know if FUSE can support NWFS in any way? > > Starting providing stress-tests on the current codebase for > NWFS/NetNCP (and report bugs found, preparing a list) could be a good > way to start the locking effort. Interested developers then can look > into such a list and provide necessary insight. 1. The in-kernel smbfs is so far behind the SMB spec that I'm not sure that it's worthwhile maintaining it. It's SMB1.x based, which is pre-Vista; SMB2.1 has been out for a while and 3.0 is rolling around the corner in the next couple years (about the same time Windows XP is going to be EOS). 2. According to reports I have from internal sources, the Apple implementation is suboptimal from a performance perspective, in part because the Apple SMB client doesn't coalesce requests. I concur on the poor performance based on personal experience because NFS beats SMB hands down on OSX (comes close to saturating the physical media with NFS, and putters along at a fraction of the link speed with CIFS on my Macbook Pro with Lion), whereas running a Windows 7 client against samba36 yields performance I would expect (saturates gigabit). YMMV, -Garrett 1. http://windows.microsoft.com/en-us/windows/products/lifecycle