From owner-freebsd-fs Sun Oct 22 10:42:40 2000 Delivered-To: freebsd-fs@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id C003537B4D7; Sun, 22 Oct 2000 10:42:37 -0700 (PDT) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id TAA68460; Sun, 22 Oct 2000 19:42:36 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id TAA34043; Sun, 22 Oct 2000 19:42:36 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Sun, 22 Oct 2000 19:42:36 +0200 (CEST) From: Marius Bendiksen To: bp@FreeBSD.org Cc: freebsd-fs@FreeBSD.org Subject: Re: kern/21807: [patches] Make System attribute correspond to SF_IMMUTABLE In-Reply-To: <200010221436.HAA95905@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have submitted a PR (with patches) with a request to change msdosfs semantics so as to make the system attribute correspond to sf_immutable in practice. I think this makes a closer mapping to what is how msdos tries to treat that attribute, and adds the ability to obtain schg semantics from an msdosfs filesystem if anyone should want to use it for something sensible. Opinions? (Context, for those who want to have a look at the PR): > Synopsis: [patches] Make System attribute correspond to SF_IMMUTABLE > > State-Changed-From-To: open->analyzed > State-Changed-By: bp > State-Changed-When: Sun Oct 22 07:34:08 PDT 2000 > State-Changed-Why: > Interesting idea. Could you please submit it to freebsd-fs ? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=21807 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Oct 23 9:52:36 2000 Delivered-To: freebsd-fs@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id 1286337B479; Mon, 23 Oct 2000 09:52:32 -0700 (PDT) Received: from owp.csus.edu (qbqjyl@[130.86.77.19]) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id JAA19061; Mon, 23 Oct 2000 09:50:38 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Message-ID: <39F46B08.808132D2@owp.csus.edu> Date: Mon, 23 Oct 2000 09:44:56 -0700 From: Joseph Scott X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Boris Popov Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When is this going to be brought into -current? Boris Popov wrote: > > Hello, > > At first, I'm want to say 'thank you' for everybody who provided > me with feedback on my work. So, here is a records from the HISTORY file > for last two releases: > > 20.10.2000 1.3.0 > - Network IO engine significantly reworked. Now it uses kernel threads > to implement 'smbiod' process which handles network traffic for each VC. > Previous model were incapable to serve large number of mount points and > didn't work well with intensive IO operations performed on a different > files on the same mount point. Special care was taken on better > usage of MP systems. > Unfortunately, kernel threads aren't supported by FreeBSD 3.X and for > now it is excluded from the list of supported systems. > - Reduce overhead caused by using single hash table for each mount point. > > 26.09.2000 1.2.8 (never released) > - More SMP related bugs are fixed. > - Make smbfs compatible with the Linux emulator. > - smbfs now known to work with IBM LanManager (special thanks to > Eugen Averin) > - Fix problem with files bigger than 2GB (reported by Lee McKenna) > - Please note that smbfs may not work properly with FreeBSD 3.X. > > New version can be downloaded from: > ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz > > -- > Boris Popov > http://www.butya.kz/~bp/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Joseph Scott joseph.scott@owp.csus.edu The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 24 22: 2:17 2000 Delivered-To: freebsd-fs@freebsd.org Received: from dsl-64-193-123-121.telocity.com (dsl-64-193-123-121.telocity.com [64.193.123.121]) by hub.freebsd.org (Postfix) with ESMTP id 3E71A37B479; Tue, 24 Oct 2000 22:02:13 -0700 (PDT) Received: (from brueggma@localhost) by dsl-64-193-123-121.telocity.com (8.11.1/8.11.1) id e9P52B703405; Wed, 25 Oct 2000 00:02:11 -0500 (CDT) (envelope-from brueggma) Date: Wed, 25 Oct 2000 00:02:10 -0500 From: Eric Brueggmann To: freebsd-questions@freebsd.org Cc: freebsd-fs@freebsd.org Subject: du/df Message-ID: <20001025000210.A2828@snoopie.yi.org> Reply-To: brueggma@snoopie.yi.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello.. Sorry for the cross post. I was wondering what could cause this: # du -hc /var | grep total 15M total # df -h /var Filesystem Size Used Avail Capacity Mounted on /dev/ad3s2e 483M 101M 343M 23% /var # sync # df -h /var Filesystem Size Used Avail Capacity Mounted on /dev/ad3s2e 483M 101M 343M 23% /var This happens every couple of weeks or so.. The difference is usually not as great as it is now. Is there any way to fix it? I don't think du is following any sym links, or anything. Thank You, Eric Brueggmann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 24 22: 7:59 2000 Delivered-To: freebsd-fs@freebsd.org Received: from baddog.yi.org (24-216-177-184.hsacorp.net [24.216.177.184]) by hub.freebsd.org (Postfix) with ESMTP id EE85C37B479; Tue, 24 Oct 2000 22:07:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by baddog.yi.org (Postfix) with ESMTP id 62F981D9F; Wed, 25 Oct 2000 01:07:55 -0400 (EDT) Date: Wed, 25 Oct 2000 01:07:54 EDT From: mike johnson To: Eric Brueggmann , freebsd-questions@FreeBSD.ORG Cc: freebsd-fs@FreeBSD.ORG Subject: Re: du/df Reply-To: ahze@slaughter.necro.edu X-Mailer: Spruce 0.6.5 for X11 w/smtpio 0.7.9 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <20001025050755.62F981D9F@baddog.yi.org> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org theres some things in /var that are not readable by normal users , you might want to try du -hc /var |grep total , or du -sh /var as root .. If you alraedy arent. On Wed, 25 Oct 2000, Eric Brueggmann wrote: > Date: Wed, 25 Oct 2000 00:02:10 -0500 > To: freebsd-questions@FreeBSD.ORG > From: Eric Brueggmann > Reply-To: brueggma@snoopie.yi.org > Subject: du/df > > Hello.. > > Sorry for the cross post. I was wondering what could cause this: > > # du -hc /var | grep total > 15M total > # df -h /var > Filesystem Size Used Avail Capacity Mounted on > /dev/ad3s2e 483M 101M 343M 23% /var > # sync > # df -h /var > Filesystem Size Used Avail Capacity Mounted on > /dev/ad3s2e 483M 101M 343M 23% /var > > This happens every couple of weeks or so.. The difference is usually not > as great as it is now. Is there any way to fix it? I don't think du is > following any sym links, or anything. > > Thank You, > Eric Brueggmann > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 24 22:59:11 2000 Delivered-To: freebsd-fs@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 65C7A37B479; Tue, 24 Oct 2000 22:59:08 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e9P5wup27852; Tue, 24 Oct 2000 22:58:56 -0700 Date: Tue, 24 Oct 2000 22:58:56 -0700 From: Brooks Davis To: mike johnson Cc: Eric Brueggmann , freebsd-questions@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: du/df Message-ID: <20001024225856.A27452@Odin.AC.HMC.Edu> References: <20001025050755.62F981D9F@baddog.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001025050755.62F981D9F@baddog.yi.org>; from ahze@baddog.yi.org on Wed, Oct 25, 2000 at 01:07:54AM -0400 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Oct 25, 2000 at 01:07:54AM -0400, mike johnson wrote: > > theres some things in /var that are not readable by normal users , > you might want to try > du -hc /var |grep total , or du -sh /var as root .. > If you alraedy arent. The most probable cause in normal operation is that a large file which is still opened was unlinked. Thus du won't find it (it's not in any directory anymore), but it is still in the filesystem. Softupdates could also cause this, but only for a relativly sort time. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Oct 25 8: 1:26 2000 Delivered-To: freebsd-fs@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id B9F2237B479; Wed, 25 Oct 2000 08:01:22 -0700 (PDT) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Wed, 25 Oct 2000 16:01:05 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 13oS2Q-0005uw-00; Wed, 25 Oct 2000 16:00:22 +0100 Date: Wed, 25 Oct 2000 16:00:22 +0100 (BST) From: Jan Grant To: Eric Brueggmann Cc: freebsd-questions@freebsd.org, freebsd-fs@freebsd.org Subject: Re: du/df In-Reply-To: <20001025000210.A2828@snoopie.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 25 Oct 2000, Eric Brueggmann wrote: > Sorry for the cross post. I was wondering what could cause this: > > # du -hc /var | grep total > 15M total > # df -h /var > Filesystem Size Used Avail Capacity Mounted on > /dev/ad3s2e 483M 101M 343M 23% /var Either softupdates (but only briefly). More likely, a rotated/deleted log file that's still being held open by a process. Try running openfiles /var (just a shell script - you can get it at http://tribble.ilrt.bris.ac.uk/~cmjg/unix/scripts/openfiles ) ...or get lsof. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Goedel would be proud - I'm both inconsistent _and_ incomplete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Oct 25 8: 5:59 2000 Delivered-To: freebsd-fs@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id EA56537B479; Wed, 25 Oct 2000 08:05:54 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA51266; Wed, 25 Oct 2000 17:05:51 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Jan Grant Cc: Eric Brueggmann , freebsd-questions@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: du/df References: From: Dag-Erling Smorgrav Date: 25 Oct 2000 17:05:49 +0200 In-Reply-To: Jan Grant's message of "Wed, 25 Oct 2000 16:00:22 +0100 (BST)" Message-ID: Lines: 9 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jan Grant writes: > ...or get lsof. hmm, or wait a couple of hours 'till I fix sockstat so it shows open files and directories as well. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Oct 25 8:11:45 2000 Delivered-To: freebsd-fs@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 439AF37B479; Wed, 25 Oct 2000 08:11:42 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA51301; Wed, 25 Oct 2000 17:11:37 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Jan Grant Cc: Eric Brueggmann , freebsd-questions@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: du/df References: From: Dag-Erling Smorgrav Date: 25 Oct 2000 17:11:37 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "25 Oct 2000 17:05:49 +0200" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dag-Erling Smorgrav writes: > Jan Grant writes: > > ...or get lsof. > hmm, or wait a couple of hours 'till I fix sockstat so it shows open > files and directories as well. Hmm, no, never mind. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 2:52:56 2000 Delivered-To: freebsd-fs@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 1FC3E37B479; Thu, 26 Oct 2000 02:52:52 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 1651628788; Thu, 26 Oct 2000 16:52:46 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 0B68028761; Thu, 26 Oct 2000 16:52:46 +0700 (ALMST) Date: Thu, 26 Oct 2000 16:52:45 +0700 (ALMST) From: Boris Popov To: Joseph Scott Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <39F46B08.808132D2@owp.csus.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 23 Oct 2000, Joseph Scott wrote: > When is this going to be brought into -current? This was planned to be done in early September, but got some troubles with import of iconv library. I can't import smbfs without i18n support because many people use it. In any way, future smbfs releases will support 4.x and recent -current. p.s. Sorry for delay but I'm overloaded with my primary work and a little bit behind my mail :( -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 5:23:22 2000 Delivered-To: freebsd-fs@freebsd.org Received: from dsl-64-193-123-121.telocity.com (dsl-64-193-123-121.telocity.com [64.193.123.121]) by hub.freebsd.org (Postfix) with ESMTP id 44FAA37B479; Thu, 26 Oct 2000 05:23:13 -0700 (PDT) Received: (from brueggma@localhost) by dsl-64-193-123-121.telocity.com (8.11.1/8.11.1) id e9QCNCV01017; Thu, 26 Oct 2000 07:23:12 -0500 (CDT) (envelope-from brueggma) Date: Thu, 26 Oct 2000 07:23:11 -0500 From: Eric Brueggmann To: freebsd-questions@freebsd.org Cc: freebsd-fs@freebsd.org Subject: df -h Message-ID: <20001026072311.A765@snoopie.yi.org> Reply-To: brueggma@snoopie.yi.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello again, I'm experiencing some more df problems. I just typed "df -h" for the second time in the past 2 days, and the machine rebooted. No messages in the logs, nothing. # uname -a FreeBSD dsl-64-193-123-121.telocity.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Fri Oct 20 12:11:58 CDT 2000 root@dsl-64-193-123-121.telocity.com:/usr/src/sys/compile/BEAST i386 Could this just be hardware failure? (disk) Eric B. > Hello.. > > Sorry for the cross post. I was wondering what could cause this: > ># du -hc /var | grep total > 15M total ># df -h /var >Filesystem Size Used Avail Capacity Mounted on >/dev/ad3s2e 483M 101M 343M 23% /var ># sync ># df -h /var >Filesystem Size Used Avail Capacity Mounted on >/dev/ad3s2e 483M 101M 343M 23% /var > >This happens every couple of weeks or so.. The difference is usually not >as great as it is now. Is there any way to fix it? I don't think du is >following any sym links, or anything. > > Thank You, > Eric Brueggmann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 8: 5:16 2000 Delivered-To: freebsd-fs@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id A0AF237B479; Thu, 26 Oct 2000 08:05:07 -0700 (PDT) Received: from localhost (scottj@localhost) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id IAA44613; Thu, 26 Oct 2000 08:04:57 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Date: Thu, 26 Oct 2000 08:04:57 -0700 (PDT) From: Joseph Scott X-Sender: scottj@pebkac.owp.csus.edu To: Boris Popov Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 26 Oct 2000, Boris Popov wrote: > On Mon, 23 Oct 2000, Joseph Scott wrote: > > > When is this going to be brought into -current? > > This was planned to be done in early September, but got some > troubles with import of iconv library. I can't import smbfs without i18n > support because many people use it. > > In any way, future smbfs releases will support 4.x and recent > -current. I've only got -stable boxes around here, I was asking simply because the sooner it makes it into -current the sooner it gets into -stable :-) Thanks again for your work on this, I look forward to seeing this in the base system. --- Joseph Scott joseph.scott@owp.csus.edu The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 10:39:15 2000 Delivered-To: freebsd-fs@freebsd.org Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 1A08E37B4C5 for ; Thu, 26 Oct 2000 10:39:12 -0700 (PDT) Received: from pain10.corp.disney.com (root@pain10.corp.disney.com [153.7.110.100]) by mail.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id e9QHd7R00172 for ; Thu, 26 Oct 2000 10:39:08 -0700 (PDT) Received: from louie.fa.disney.com by pain.corp.disney.com with ESMTP for freebsd-fs@freebsd.org; Thu, 26 Oct 2000 10:39:42 -0700 Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by louie.fa.disney.com (8.9.2/8.9.2) with ESMTP id KAA11108 for ; Thu, 26 Oct 2000 10:39:06 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from snoopy.fan.fa.disney.com by mercury.fan.fa.disney.com for freebsd-fs@freebsd.org; Thu, 26 Oct 2000 10:39:06 -0700 From: Jim Pirzyk Organization: Walt Disney Feature Animation To: freebsd-fs@freebsd.org Subject: Autofs on FreeBSD Date: Thu, 26 Oct 2000 10:38:54 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00102610391007.17987@snoopy.fan.fa.disney.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry Lambert said that I shoudl contact this list about any work on AutoFS, so here is my orignal message to freebsd-hackers. Our biggest problem with amd is the use of sym links instead of mounts in place. Is there anyone working on a mount in place automounter? What about the autofs code that was removed from amd? We move data around every week and we need the users to see the map name and not the mount name (ie. /data/ada18 instead of /tmp_mnt/aj/bay_l0g2). The data next week may be on /tmp_mnt/oilspot/january_b1g1 instead. Not only does 'at' have this problem but so does csh & tcsh. Thanks - JimP ---------- Forwarded Message ---------- Subject: AutoFS on FreeBSD Date: Tue, 24 Oct 2000 17:24:06 -0700 From: Jim Pirzyk I was wondering if there is anyone working on AutoFS for FreeBSD. We currently have 4 studios with around 1000 unix systems of all kinds. Currently there are only 2 OSes that do not have autofs, FreeBSD and one that is known for its number crunching capabilties (and those are being phased out of production). Amd will not meet our needs because of the use of sym links. This is why AutoFS was written in the first place. I quote the 1993 USENIX paper on AutoFS (check http://www.usenix.org/publications/library/proceedings/cinci93/full_papers/callaghan.txt for the full paper). Symbolic links A single automount daemon can service many mountpoints. At each mountpoint the daemon associates a map, and emulates either a symbolic link (direct map) or a directory of symbolic links (indirect map). The symbolic links point to a directory where the automounter performs NFS mounts - /tmp_mnt or /a. The automounter unmounts what it considers to be "idle" mounts - those that have not been active - or that can be unmounted (not busy). As long as all references to these mounts are made through the daemon mountpoint, the dae- mon can replace the mounts as necessary. However, if a process invokes the getwd() function to obtain the path of the current directory while in an automounted filesystem, it will obtain a "/tmp_mnt/..." path. If this "back door" path is cached and used sometime later, there is no guarantee that the filesystem will still be mounted there. The automounter cannot detect references to empty mount- points unless they are made through the automounter's mountpoint. A common victim of this behavior is the at com- mand. It uses the pwd command to record the current directory so that it can be cd'ed to for subsequent invocation of the script. The symbolic links also confuse users because "/tmp_mnt" frequently appears as a prefix to the current directory. Various workarounds have been proposed for this problem. The most common was for the getwd() function to strip prepended "/tmp_mnt/" from paths. This workaround didn't take into account the effect of the automounter's -M flag that allowed users to specify a directory other than "/tmp_mnt/". It is also questionable whether the semantics of getwd() should be changed this way. The symbolic links present a problem for relative references between separate automounter mounts. For instance given the two directories /home/bob and /home/carol it seems reasonable that Bob should be able to "cd ../carol" but this will fail if Carol's directory isn't already mounted. If no one is using it, how is it looked apon if AutoFS was ported from Linux (with the GPL and that stuff) or would a complete rewrite be better? - JimP -- --- @(#) $Id: dot.signature,v 1.9 2000/07/10 16:43:05 pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------------------------------- _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 12: 2:46 2000 Delivered-To: freebsd-fs@freebsd.org Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by hub.freebsd.org (Postfix) with ESMTP id 8C2E137B479 for ; Thu, 26 Oct 2000 12:02:43 -0700 (PDT) Received: from shekel.mcl.cs.columbia.edu (shekel.mcl.cs.columbia.edu [128.59.18.15]) by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id PAA15722; Thu, 26 Oct 2000 15:02:41 -0400 (EDT) Received: (from ezk@localhost) by shekel.mcl.cs.columbia.edu (8.9.3/8.9.3) id PAA10501; Thu, 26 Oct 2000 15:02:40 -0400 (EDT) Date: Thu, 26 Oct 2000 15:02:40 -0400 (EDT) Message-Id: <200010261902.PAA10501@shekel.mcl.cs.columbia.edu> From: Erez Zadok To: Jim Pirzyk Cc: freebsd-fs@FreeBSD.ORG, ion@cs.columbia.edu Subject: Re: Autofs on FreeBSD In-reply-to: Your message of "Thu, 26 Oct 2000 10:38:54 PDT." <00102610391007.17987@snoopy.fan.fa.disney.com> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <00102610391007.17987@snoopy.fan.fa.disney.com>, Jim Pirzyk writes: > Terry Lambert said that I shoudl contact this list about > any work on AutoFS, so here is my orignal message to > freebsd-hackers. If anyone is going to do work on autofs for FreeBSD, keep it in this list (or let me know which list to go on). I've used different versions of autofs on different systems with and without Amd. I have many comments on how to get it right the first time, so you won't have to do two iterations like Sun, or three like Linux. > Our biggest problem with amd is the use of sym links instead > of mounts in place. Is there anyone working on a mount > in place automounter? What about the autofs code that > was removed from amd? What autofs code was removed from amd? I don't know of any which was either added or removed for FreeBSD (not on my official distribution). Currently, am-utils fully supports autofs on Linux, and partially on Solaris. We're planning on completing the Solaris support for autofs in the coming months. > We move data around every week and we need the users > to see the map name and not the mount name (ie. > /data/ada18 instead of /tmp_mnt/aj/bay_l0g2). The > data next week may be on /tmp_mnt/oilspot/january_b1g1 > instead. > > Not only does 'at' have this problem but so does csh & tcsh. There are some partial solutions: check am-utils's pawd program and "amq -w". > Thanks > > - JimP Erez. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 12:36:45 2000 Delivered-To: freebsd-fs@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 5255837B479; Thu, 26 Oct 2000 12:36:41 -0700 (PDT) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA15519; Thu, 26 Oct 2000 12:36:19 -0700 (PDT) (envelope-from DougB@gorean.org) Date: Thu, 26 Oct 2000 12:36:18 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n37.san.rr.com To: Eric Brueggmann Cc: freebsd-questions@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: df -h In-Reply-To: <20001026072311.A765@snoopie.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 26 Oct 2000, Eric Brueggmann wrote: > Hello again, > > I'm experiencing some more df problems. I just typed "df -h" for the > second time in the past 2 days, and the machine rebooted. No messages in the > logs, nothing. That's really bad. Could you take a look at the instructions for setting up kernel debugging in the handbook (dumpdev in /etc/rc.conf*, etc.) and add the following to your kernel config: # Add extra debugging information to the kernel options DIAGNOSTIC # The INVARIANTS option is used in a number of source files to enable # extra sanity checking of internal structures. options INVARIANTS options INVARIANT_SUPPORT # Kernel debugger options DDB # Don't drop into DDB for a panic. Intended for unattended operation # where you may want to drop to DDB from the console, but still want # the machine to recover from a panic options DDB_UNATTENDED The last option is only necessary if you are concerned about this happening when you are not at the console. It would actually be better to leave this out if you are going to have physical access to the machine. Assuming that you can actually get information out of DDB, please send it to freebsd-stable@freebsd.org. I realize that this is a lot of work for you, but really it's the only way we can get the data we need to trace the problem. I alias df to 'df -h' on all my machines, running many vintages of RELENG_4 and RELENG_5, and I've never seen this panic, which is why I think the stack trace of a dead kernel is our only option here. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 19:48:59 2000 Delivered-To: freebsd-fs@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id CA11737B479 for ; Thu, 26 Oct 2000 19:48:57 -0700 (PDT) Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0006-Fujitsu Gateway) id LAA07264 for ; Fri, 27 Oct 2000 11:48:56 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) From: tsuchiya@flab.fujitsu.co.jp Received: from aiko.kawasaki.flab.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0010-Fujitsu Domain Master) id LAA09763 for ; Fri, 27 Oct 2000 11:48:55 +0900 (JST) (envelope-from tsuchiya@flab.fujitsu.co.jp) Received: (from tsuchiya@localhost) by aiko.kawasaki.flab.fujitsu.co.jp (8.8.5/3.5Wpl7) id LAA05189 for freebsd-fs@FreeBSD.ORG; Fri, 27 Oct 2000 11:45:38 +0900 Date: Fri, 27 Oct 2000 11:45:38 +0900 Message-Id: <200010270245.LAA05189@aiko.kawasaki.flab.fujitsu.co.jp> To: freebsd-fs@FreeBSD.ORG Subject: validation tool? Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Is there any validation tool, that checks if system calls work as written in man pages? We have developed a file system and would like to know if it returns right errors in various conditions. Thank you, Yoshi --- Tsuchiya Yoshihiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Oct 26 20:11:38 2000 Delivered-To: freebsd-fs@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B8A1C37B479 for ; Thu, 26 Oct 2000 20:11:35 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id OAA12831; Fri, 27 Oct 2000 14:11:27 +1100 Date: Fri, 27 Oct 2000 14:11:15 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: tsuchiya@flab.fujitsu.co.jp Cc: freebsd-fs@FreeBSD.ORG Subject: Re: validation tool? In-Reply-To: <200010270245.LAA05189@aiko.kawasaki.flab.fujitsu.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 27 Oct 2000 tsuchiya@flab.fujitsu.co.jp wrote: > Is there any validation tool, that checks if system calls work as > written in man pages? > We have developed a file system and would like to know if it returns > right errors in various conditions. NIST PCTS is useful for the syscalls specified in POSIX.1-1990. The 1996 version of it was named something like NP_distr.gz. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 1:40:58 2000 Delivered-To: freebsd-fs@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id E292237B479 for ; Fri, 27 Oct 2000 01:40:55 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id BAA09798; Fri, 27 Oct 2000 01:41:22 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp05.primenet.com, id smtpdAAA8LaGht; Fri Oct 27 01:41:16 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id BAA25886; Fri, 27 Oct 2000 01:40:47 -0700 (MST) From: Terry Lambert Message-Id: <200010270840.BAA25886@usr09.primenet.com> Subject: Re: validation tool? To: tsuchiya@flab.fujitsu.co.jp Date: Fri, 27 Oct 2000 08:40:36 +0000 (GMT) Cc: freebsd-fs@FreeBSD.ORG In-Reply-To: <200010270245.LAA05189@aiko.kawasaki.flab.fujitsu.co.jp> from "tsuchiya@flab.fujitsu.co.jp" at Oct 27, 2000 11:45:38 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is there any validation tool, that checks if system calls work as > written in man pages? > We have developed a file system and would like to know if it returns > right errors in various conditions. The SVID III validation suite will do this for SVID compliant UNIX systems (SVR4 derived systems); it is only available under license, and requires TET (Test Environment Toolkit), which is free. There is also the PCTS (POSIX Conformance Test Suite), which is published by the U.S. NIST (National Institute of Standards and Technology). This is available for free download; you can find it by going to Altavist and querying for: +PCTS +NIST +download I have also written a tool, which others have updated. It is a test framework, whose intent is to look for kernel memory leaks by examining memory allocations in the kernel before and after system calls. It's probably not what you are looking for, but it's called "TESTSET", and is available from: http://people.FreeBSD.org/~terry/testset.txt http://people.FreeBSD.org/~terry/testset.tar.gz.uu It could be useful for a file system, since they do allocations and deallocations, but you will need to round-trip the code. If you are going to "roll your own", I would strongly recommend using "TET", or better, "ETET", as a basis for your testing framework (both are a product of the now defunct UNIX International, which I saved before their FTP server went down; they are now all over the net in various places, but the canonical location is at Digiboard's FTP server). Finally, there is C++ code available in the comp.sources.unix archives, which is capable of doing branch path validation on C code. You basically run your code through the C preprocessor to strip out any occurances of unexpanded macros, and then run the program on it. It will create test cases for every branch path in the code, and this will mean that the tests it generates will have 100% code coverage. You will have to either run the code in kernel space with the FS, or you will have to have glue code that packages up the calls into system calls which, when they are unpackaged by the kernel, will result in the same function calls against the branch path. Sorry, but FreeBSD still doesn't support user mode debugging of VFS modules, at this time (I could tell you what you'd have to do to support that, if you wanted, as well, but it is primarily not useful on anything but pure stacking layers, unless you do a lot of work to implement the bottom end kernel interface emulation in user space). Hope this helps.. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 8:15:55 2000 Delivered-To: freebsd-fs@freebsd.org Received: from zeus.lpa.com (mail.lpa.com [12.3.233.134]) by hub.freebsd.org (Postfix) with ESMTP id E2E7437B479; Fri, 27 Oct 2000 08:15:42 -0700 (PDT) Received: from xelus.com ([10.4.5.232]) by zeus.lpa.com (Netscape Messaging Server 4.15) with ESMTP id G33H1700.9FA; Fri, 27 Oct 2000 11:15:07 -0400 Date: Fri, 27 Oct 2000 11:15:39 -0400 From: Shawn Halpenny Cc: Boris Popov , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released Message-ID: <20001027111539.A391@nightrain.xelus.com> References: <39F46B08.808132D2@owp.csus.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39F46B08.808132D2@owp.csus.edu> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Speaking of smbfs, has anyone else run into an odd bug using it in 4.1.1-STABLE? Occasionally, if I run 'df' or try to access the directories (e.g. using 'ls') for an smbfs mount after a period of time during which there were no accesses across that mount point (e.g. mount, don't touch it for an hour, then try 'df'), my machine will reboot after a few seconds. No panic message or anything--it's just like I pressed the reset button. Incidentally, under smbfs-1.2.7, the above scenario only caused 'ls' to display 'broken pipe' and I could remount that share and things would be fine. 'df' would still work without any noticeable difference. Don't have any idea about starting to troubleshoot this one. -- Shawn Halpenny | Maniacal@I Ache, Ohm | "Universal Danger!" +- - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - \ | vi:G3kfM~lxfAPXh~l~2x2FirllpfcxlrifaprmfOX~Xp2hr.lrcelyl2p - - - - - - - -| fU~X~refsPprnlxppri2lxlpr,pFrpprrfaPlpfiprgllxp~3Xlpfndw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 8:28:24 2000 Delivered-To: freebsd-fs@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6250937B4C5; Fri, 27 Oct 2000 08:28:17 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA20853; Fri, 27 Oct 2000 11:27:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 27 Oct 2000 11:27:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Eric Brueggmann Cc: freebsd-questions@freebsd.org, freebsd-fs@freebsd.org Subject: Re: df -h In-Reply-To: <20001026072311.A765@snoopie.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org About 24 hours after you sent this, Shawn Halpenny sent e-mail observing that he was experiencing it when using smbfs. Are you using smbfs, another file system, or only normal FFS/MFS partitions? Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Thu, 26 Oct 2000, Eric Brueggmann wrote: > Hello again, > > I'm experiencing some more df problems. I just typed "df -h" for the > second time in the past 2 days, and the machine rebooted. No messages in the > logs, nothing. > > # uname -a > FreeBSD dsl-64-193-123-121.telocity.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Fri Oct 20 12:11:58 CDT 2000 root@dsl-64-193-123-121.telocity.com:/usr/src/sys/compile/BEAST i386 > > Could this just be hardware failure? (disk) > > > Eric B. > > > Hello.. > > > > Sorry for the cross post. I was wondering what could cause this: > > > ># du -hc /var | grep total > > 15M total > ># df -h /var > >Filesystem Size Used Avail Capacity Mounted on > >/dev/ad3s2e 483M 101M 343M 23% /var > ># sync > ># df -h /var > >Filesystem Size Used Avail Capacity Mounted on > >/dev/ad3s2e 483M 101M 343M 23% /var > > > >This happens every couple of weeks or so.. The difference is usually not > >as great as it is now. Is there any way to fix it? I don't think du is > >following any sym links, or anything. > > > > Thank You, > > Eric Brueggmann > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-fs" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 10: 2: 7 2000 Delivered-To: freebsd-fs@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 5110737B479; Fri, 27 Oct 2000 10:02:02 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA16720; Fri, 27 Oct 2000 12:01:49 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 27 Oct 2000 12:01:48 -0500 (CDT) From: Chris Dillon To: Shawn Halpenny Cc: Boris Popov , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <20001027111539.A391@nightrain.xelus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 27 Oct 2000, Shawn Halpenny wrote: > Speaking of smbfs, has anyone else run into an odd bug using it in > 4.1.1-STABLE? Occasionally, if I run 'df' or try to access the > directories (e.g. using 'ls') for an smbfs mount after a period > of time during which there were no accesses across that mount > point (e.g. mount, don't touch it for an hour, then try 'df'), my > machine will reboot after a few seconds. No panic message or > anything--it's just like I pressed the reset button. I've not had it panic on me under those situations, but it does do weird things. I think I'd either get an empty directory listing, or it would say "path too long" or something like that and any relative path stuff like "cd .." wouldn't work. I'd have to give a full path to get where I wanted to go, even if it was the _same_ directory. I've also had cases where I was drilling down through the directories in the Save File dialog in Navigator and I would get incomplete directory listings. Also, it seems, if I try to save a file that way, the file ends up corrupted. If I save it to a local filesystem and then move it over manually, its fine. Other than those small annoyances, it seems to work great. Oh yeah, I've noticed one more thing. When you're at the root of a mount, you can cd into a directory using any case, but if you get the case wrong, you don't get a listing. Here's an example: root@tech43 [/smb/rsisfs1/d]# ls ADMINNOTIFY/ REB98/ SECURITY/ SHARES/ tmpacls.bat* CPQIS1/ RECYCLER/ SETACLS.BAT* TEMP/ root@tech43 [/smb/rsisfs1/d]# cd reb98 root@tech43 [/smb/rsisfs1/d/reb98]# ls root@tech43 [/smb/rsisfs1/d/reb98]# cd ../REB98 root@tech43 [/smb/rsisfs1/d/REB98]# ls ARCHIVE/ PACKAGES/ AUTOEXEC.BAT* PCRDIST/ BATCH/ REBMIR.LOG* ... and so on ... root@tech43 [/smb/rsisfs1/d/REB98]# cd packages packages: No such file or directory. root@tech43 [/smb/rsisfs1/d/REB98]# cd PACKAGES root@tech43 [/smb/rsisfs1/d/REB98/PACKAGES]# So... the case-insensitivity only happens at the root of the mount. Should it happen everywhere? It'd be nice if it did. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 11:58:38 2000 Delivered-To: freebsd-fs@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6734B37B479 for ; Fri, 27 Oct 2000 11:58:35 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id OAA23827; Fri, 27 Oct 2000 14:58:33 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 27 Oct 2000 14:58:33 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-fs@FreeBSD.org, Boris Popov Subject: Re: df -h (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Boris, Apparently this didn't get CC'd back to the list. It looks like the df issue may indeed be associated with smbfs. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Fri, 27 Oct 2000 13:45:01 -0500 From: Eric Brueggmann To: Robert Watson Subject: Re: df -h YES!!! ;-) smbfs-1.3.0. I just started using smbfs-1.3.0 and I just installed a new scsi card Adaptec 29160, and installed world.. so I couldn't nail it down. Please, (pretty please) keep me in the loop. Eric B. On Fri, Oct 27, 2000 at 11:27:55AM -0400, Robert Watson wrote: > > About 24 hours after you sent this, Shawn Halpenny > sent e-mail observing that he was experiencing it when using smbfs. Are > you using smbfs, another file system, or only normal FFS/MFS partitions? > > Thanks, > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > On Thu, 26 Oct 2000, Eric Brueggmann wrote: > > > Hello again, > > > > I'm experiencing some more df problems. I just typed "df -h" for the > > second time in the past 2 days, and the machine rebooted. No messages in the > > logs, nothing. > > > > # uname -a > > FreeBSD dsl-64-193-123-121.telocity.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Fri Oct 20 12:11:58 CDT 2000 root@dsl-64-193-123-121.telocity.com:/usr/src/sys/compile/BEAST i386 > > > > Could this just be hardware failure? (disk) > > > > > > Eric B. > > > > > Hello.. > > > > > > Sorry for the cross post. I was wondering what could cause this: > > > > > ># du -hc /var | grep total > > > 15M total > > ># df -h /var > > >Filesystem Size Used Avail Capacity Mounted on > > >/dev/ad3s2e 483M 101M 343M 23% /var > > ># sync > > ># df -h /var > > >Filesystem Size Used Avail Capacity Mounted on > > >/dev/ad3s2e 483M 101M 343M 23% /var > > > > > >This happens every couple of weeks or so.. The difference is usually not > > >as great as it is now. Is there any way to fix it? I don't think du is > > >following any sym links, or anything. > > > > > > Thank You, > > > Eric Brueggmann > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-fs" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 12: 1:35 2000 Delivered-To: freebsd-fs@freebsd.org Received: from dsl-64-193-123-121.telocity.com (dsl-64-193-123-121.telocity.com [64.193.123.121]) by hub.freebsd.org (Postfix) with ESMTP id 4451B37B479; Fri, 27 Oct 2000 12:01:29 -0700 (PDT) Received: (from brueggma@localhost) by dsl-64-193-123-121.telocity.com (8.11.1/8.11.1) id e9RJ1Su91284; Fri, 27 Oct 2000 14:01:28 -0500 (CDT) (envelope-from brueggma) Date: Fri, 27 Oct 2000 14:01:28 -0500 From: Eric Brueggmann To: Robert Watson Cc: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org Subject: Re: df -h Message-ID: <20001027140128.A90763@snoopie.yi.org> Reply-To: brueggma@snoopie.yi.org References: <20001026072311.A765@snoopie.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@freebsd.org on Fri, Oct 27, 2000 at 11:27:55AM -0400 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes sir: # ls -la smbfs-1.3.0.tar -rw-r--r-- 1 root samba 716800 Oct 19 22:58 smbfs-1.3.0.tar # uname -a FreeBSD dsl-64-193-123-121.telocity.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Th u Oct 26 23:36:44 CDT 2000 root@dsl-64-193-123-121.telocity.com:/usr/src/sys /compile/BEAST i386 Since the previous post, I have found out that df, du, and quota all cause the machine to reboot. But the machine only reboots using the above commands after X mins of uptime. Eric B. Please let me know if you need more info. On Fri, Oct 27, 2000 at 11:27:55AM -0400, Robert Watson wrote: > > About 24 hours after you sent this, Shawn Halpenny > sent e-mail observing that he was experiencing it when using smbfs. Are > you using smbfs, another file system, or only normal FFS/MFS partitions? > > Thanks, > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > On Thu, 26 Oct 2000, Eric Brueggmann wrote: > > > Hello again, > > > > I'm experiencing some more df problems. I just typed "df -h" for the > > second time in the past 2 days, and the machine rebooted. No messages in the > > logs, nothing. > > > > # uname -a > > FreeBSD dsl-64-193-123-121.telocity.com 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Fri Oct 20 12:11:58 CDT 2000 root@dsl-64-193-123-121.telocity.com:/usr/src/sys/compile/BEAST i386 > > > > Could this just be hardware failure? (disk) > > > > > > Eric B. > > > > > Hello.. > > > > > > Sorry for the cross post. I was wondering what could cause this: > > > > > ># du -hc /var | grep total > > > 15M total > > ># df -h /var > > >Filesystem Size Used Avail Capacity Mounted on > > >/dev/ad3s2e 483M 101M 343M 23% /var > > ># sync > > ># df -h /var > > >Filesystem Size Used Avail Capacity Mounted on > > >/dev/ad3s2e 483M 101M 343M 23% /var > > > > > >This happens every couple of weeks or so.. The difference is usually not > > >as great as it is now. Is there any way to fix it? I don't think du is > > >following any sym links, or anything. > > > > > > Thank You, > > > Eric Brueggmann > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-fs" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 15:23:51 2000 Delivered-To: freebsd-fs@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id CD08A37B479; Fri, 27 Oct 2000 15:23:48 -0700 (PDT) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id SAA25320; Fri, 27 Oct 2000 18:23:46 -0400 (EDT) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id SAA16354; Fri, 27 Oct 2000 18:21:24 -0400 (EDT) Date: Fri, 27 Oct 2000 18:21:24 -0400 (EDT) From: Kenneth W Cochran Message-Id: <200010272221.SAA16354@world.std.com> To: freebsd-fs@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Upcoming 4.2, Linux ext2 fs Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello -stable & -fs, With the upcoming 4.2 freeze, what is the status of any improvements in support for the Linux ext2 filesystem? As of 4.1.1-stable 2000/10/22, the only ext2 filesystem FreeBSD can mount r/w is an "older version" & without some "features...("sparse superblock," etc.)" I *can* make a filesystem (using Linux) as the "older" version, & r/w mounting & use seems to be ok.. For now (with -stable as of 2000/10/22) Mounting the "newer version" ext2 filesystem readonly seems to work ok. Thanks, -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 16:57:34 2000 Delivered-To: freebsd-fs@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 77F3B37B479; Fri, 27 Oct 2000 16:57:29 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id QAA07200; Fri, 27 Oct 2000 16:55:41 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpdAAA2CayNl; Fri Oct 27 16:53:22 2000 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id QAA02252; Fri, 27 Oct 2000 16:55:01 -0700 (MST) From: Terry Lambert Message-Id: <200010272355.QAA02252@usr01.primenet.com> Subject: Re: smbfs-1.3.0 released To: cdillon@wolves.k12.mo.us (Chris Dillon) Date: Fri, 27 Oct 2000 23:55:01 +0000 (GMT) Cc: malachai@iname.com (Shawn Halpenny), bp@butya.kz (Boris Popov), freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG In-Reply-To: from "Chris Dillon" at Oct 27, 2000 12:01:48 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Oh yeah, I've noticed one more thing. When you're at the root of a > mount, you can cd into a directory using any case, but if you get the > case wrong, you don't get a listing. Here's an example: [ ... ] > So... the case-insensitivity only happens at the root of the mount. > Should it happen everywhere? It'd be nice if it did. :-) Ha! The full path is sent over the wire. The attempt to be "case sensitive on storage, case insensitive on lookup" is inhernetly flawed. The way this works on OSs which support it is that the globbing occurs in the kernel. This lets the case folding occur before the data is returned. The difference is that if you are iterating and comparing in user space, you will get a failure, but if you are doing an explicit VOP_LOOKUP in kernel space, the case folding will work. The problem is that you don't really get a directory handle object, like you get an inode in NFS, since in a DOS FS, and thus in the wire externalization of a DOS FS, which is what SMB gives you, the directory entry itself _is_ the inode, not a pointer to an independent object which dereferences to the inode. I suspect that this is at the heart of your lookup problems, given the way that UNIX programs tend to put in what they were given out. I think that if you disable the attempted case folding in the SMBFS VOP_LOOKUP code, your problem will go away. Note: things which reference explicit names use VOP_LOOKUP, while things which iterate directories use VOP_READDIR. I suspect that you will see similar problems on attempts to rename things, because of this. NB: Another approach would be to fold everything to lower case in both VOP_LOOKUP and VOP_READDIR; this could be accomplished using a mount option. If you wanted to be more Windows-like, you could make the first letter upper case, and subsequent letters lower case. NNB: The behaviour will also depend on the server you are using; some servers can return both the short (8.3) and long names over SMB, and others can only return the short names. NNNB: If you are using a Samba server as the server, and short names, you are probably screwed, since short names on a Samba server are synthetic, and indeterminately so. On a Windows box, if I rename (short:long) "PROGRA~1":"Program Files" to "PROGRA~7", I get "PROGRA~7":"PROGRA~7"; if I then rename "PROGRA~7" to "Program Files", I get "PROGRA~7":"Program Files". Since the Samba short namespace is synthetic even if the UNIX FS underneath supports both name spaces (since the UNIX name API is handicapped, compared to the Macintosh or Windows API), you will get a short name based on the inode number. --- As to the df/du problem, I'd suggest hacking VFS_STAT to return fake data, and then figure out why it's failing so catastrophically, since the problem is there. I suspect the problem is that it is an old VFS_STAT call that is being called, and that a new VFS_STAT struct is being copied out in all cases, instead of making sure it is old vs. new, and doing the right thing, and the resulting buffer overrun stomps on something important. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 18:55:40 2000 Delivered-To: freebsd-fs@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id ED0ED37B479; Fri, 27 Oct 2000 18:55:36 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 27A0628DA0; Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 175EE28D7E; Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) Date: Sat, 28 Oct 2000 08:55:33 +0700 (ALMST) From: Boris Popov To: Shawn Halpenny Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <20001027111539.A391@nightrain.xelus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 27 Oct 2000, Shawn Halpenny wrote: > Speaking of smbfs, has anyone else run into an odd bug using it in > 4.1.1-STABLE? Occasionally, if I run 'df' or try to access the > directories (e.g. using 'ls') for an smbfs mount after a period of > time during which there were no accesses across that mount point (e.g. > mount, don't touch it for an hour, then try 'df'), my machine will > reboot after a few seconds. No panic message or anything--it's just > like I pressed the reset button. I think that I've found possible cause of this problem and 1.3.1 will be released at this weekend. > Incidentally, under smbfs-1.2.7, the above scenario only caused 'ls' > to display 'broken pipe' and I could remount that share and things Yes, 'broken pipe' was a bug and now it should work properly. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 27 19:14:21 2000 Delivered-To: freebsd-fs@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 2356137B479; Fri, 27 Oct 2000 19:14:13 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id AFE3628DA0; Sat, 28 Oct 2000 09:14:09 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id A41D228D7E; Sat, 28 Oct 2000 09:14:09 +0700 (ALMST) Date: Sat, 28 Oct 2000 09:14:09 +0700 (ALMST) From: Boris Popov To: Terry Lambert Cc: Chris Dillon , Shawn Halpenny , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: smbfs-1.3.0 released In-Reply-To: <200010272355.QAA02252@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 27 Oct 2000, Terry Lambert wrote: > > So... the case-insensitivity only happens at the root of the mount. > > Should it happen everywhere? It'd be nice if it did. :-) > > Ha! > > The full path is sent over the wire. > > The attempt to be "case sensitive on storage, case insensitive on > lookup" is inhernetly flawed. Actually, smbfs doesn't try to be case insensitive. At this moment it merely passes file names with possible charset translation. If long names is not used (WfWg for example), then file names converted to upper case. nwfs have more complex case management features (see mount_nwfs(4) for '-c' option). > The difference is that if you are iterating and comparing in > user space, you will get a failure, but if you are doing an > explicit VOP_LOOKUP in kernel space, the case folding will work. Hmm, why ? > The problem is that you don't really get a directory handle > object, like you get an inode in NFS, since in a DOS FS, and > thus in the wire externalization of a DOS FS, which is what SMB > gives you, the directory entry itself _is_ the inode, not a > pointer to an independent object which dereferences to the inode. > I think that if you disable the attempted case folding in the > SMBFS VOP_LOOKUP code, your problem will go away. Not exactly so - case sensitivity depends on server, for most servers ls /A and ls /a are the same, but NT have strange behavior for root directory and not all directories are case insensitive. > NB: Another approach would be to fold everything to lower case > in both VOP_LOOKUP and VOP_READDIR; this could be accomplished > using a mount option. If you wanted to be more Windows-like, > you could make the first letter upper case, and subsequent > letters lower case. I'm unsure if this correct, because long file names used on windows platform may have more than one upper case letter (Program Files for example). > NNNB: If you are using a Samba server as the server, and short > names, you are probably screwed, since short names on a Samba > server are synthetic, and indeterminately so. On a Windows > box, if I rename (short:long) "PROGRA~1":"Program Files" to > "PROGRA~7", I get "PROGRA~7":"PROGRA~7"; if I then rename > "PROGRA~7" to "Program Files", I get "PROGRA~7":"Program Files". > Since the Samba short namespace is synthetic even if the UNIX > FS underneath supports both name spaces (since the UNIX name > API is handicapped, compared to the Macintosh or Windows API), > you will get a short name based on the inode number. Correct and it is not recommended to use 8.3 name space with Samba. > As to the df/du problem, I'd suggest hacking VFS_STAT to return > fake data, and then figure out why it's failing so catastrophically, > since the problem is there. I suspect the problem is that it is > an old VFS_STAT call that is being called, and that a new VFS_STAT > struct is being copied out in all cases, instead of making sure it > is old vs. new, and doing the right thing, and the resulting > buffer overrun stomps on something important. No, this is not related. The same things will happen on all SMB requests if server dropped the connection and it seems to be fixed in the upcoming smbfs-1.3.1. On a side note I'm unsure why NT server drops the connection if client doesn't send any request in XX minutes (for example Samba uses NetBIOS keepalive packets). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sat Oct 28 2:11: 4 2000 Delivered-To: freebsd-fs@freebsd.org Received: from port.teleport.ee (port.teleport.ee [212.107.32.157]) by hub.freebsd.org (Postfix) with ESMTP id 0C6AF37B666 for ; Sat, 28 Oct 2000 02:11:01 -0700 (PDT) Received: from olja (ppp41104.tele2.ee [212.107.41.104]) by port.teleport.ee (8.9.3/8.8.7) with SMTP id LAA18507 for ; Sat, 28 Oct 2000 11:10:57 +0200 Message-Id: <200010280910.LAA18507@port.teleport.ee> From: olja To: freebsd-fs@freebsd.org Subject: privet! X-Mailer: Outlook Express Reply-To: olja@mail.ru Date: Sat, 28 Oct 2000 11:08:14 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org kak dela? davno tebja ne vidno bylo. kak zizn, napishi o sebe.... a ja shas uchus, teper vremja est v internete sidet :) ja teper chasto v chate sizu http://ultra.profic.ee/ ladno, poka Olja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message