From owner-freebsd-fs Sun Oct 29 21:40:57 2000 Delivered-To: freebsd-fs@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DE27D37B479; Sun, 29 Oct 2000 21:40:50 -0800 (PST) Received: from newsguy.com (p05-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.134]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id OAA07157; Mon, 30 Oct 2000 14:40:40 +0900 (JST) Message-ID: <39FD097F.FCFDEF4A@newsguy.com> Date: Mon, 30 Oct 2000 14:39:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: brueggma@snoopie.yi.org Cc: freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: df -h References: <20001026072311.A765@snoopie.yi.org> <20001027140128.A90763@snoopie.yi.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eric Brueggmann wrote: > > 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. Well, this is not my bailiwick, but I must point out that this is _not_ enough info. Please excuse me if I appear to be rude, for I'm only trying to help you get _results_ when you have a problem. You won't get results if the feedback you provide is not adequate. You see, maybe the problem is with your computer. Maybe it's some specific option in your setup. There is a huge number of possible causes to the problem, which result in the problem not being reproducable elsewhere. Besides, committers are busy people, and spending hours trying to reproduce a bug is an unlikely proposition. So, the first problem with the above is that the instructions on reproducing it _are not clear_. For instance, "X minutes". Well, suppose I try to reproduce the problem without success. It might be that "X minutes" is more than I waited. It might be that "X minutes" depends on how much the fs is used, not the actual uptime. It might be that the problem is a hardware problem on your computer that is only exercised by some exoteric code. It might be all sorts of things. So, at that point, I don't know what to do. Of course, I _could_ give it a try, and ask for more information if I can't reproduce it at first try. But I won't. I have features I want to code, I have clear bug reports to look into, and I even have a Life (well, actually, I don't, but some of us do :). So, when I see a bug report like this, I'll simply ignore it in favor of something which I won't be wasting my time with. So, how do you go about it? First, try to find out what *DOESN'T* cause the problem to manifest itself. It fails with smbfs, right? Does it fail without smbfs? Does it fail with a GENERIC kernel instead of whatever specific kernel you are using? If it doesn't fail at first, what makes a difference? Some specific amount of time? Network usage? FS usage? Try to track down what's the last straw that causes it to start rebooting. If you think that's too time consuming for you, well, it is. But I have news for you. It's time consuming for us too, and we are _not_ being paid to look into it. Then you report the exact conditions necessary for the problem to manifest itself, as well as what doesn't cause the problem. And this is only the very minimum. Hardware descriptions, dmesg, kernel configuration file, configuration files and hardware description related to whatever you have having problem with, etc are all useful. If the problem happened to everyone, it stands to reason the author of the code would have found it already. So, generally speaking, you must assume the problem is NOT happening to everyone, and is related to something specific in your system. And this still isn't a *good* problem report, just an acceptable one. A *good* problem report is one in which you go to the trouble of making a kernel with the debug and extra checks options available, such as INVARIANTS and DDB, and then getting a backtrace of whatever panic you have. And while you might not be getting panics now, maybe you'll get them with INVARIANTS and DIAGNOSE. Maybe you are already using those options but, you see, you didn't mention that, so I have no way of knowing. HTH. HAND. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@world.wide.bsdconspiracy.net He has been convicted of criminal possession of a clue with intent to distribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 31 1:14:52 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 172F137B4CF; Tue, 31 Oct 2000 01:14:46 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id CAA02989; Tue, 31 Oct 2000 02:12:56 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpdAAAPDaG0f; Tue Oct 31 02:12:52 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id CAA28652; Tue, 31 Oct 2000 02:14:36 -0700 (MST) From: Terry Lambert Message-Id: <200010310914.CAA28652@usr02.primenet.com> Subject: Re: smbfs-1.3.0 released To: bp@butya.kz (Boris Popov) Date: Tue, 31 Oct 2000 09:14:35 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), cdillon@wolves.k12.mo.us (Chris Dillon), malachai@iname.com (Shawn Halpenny), freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG In-Reply-To: from "Boris Popov" at Oct 28, 2000 09:14:09 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 > > 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 ? UNIX globbing occurs in user space. Windows globbing, like VMS globbing, happens in the kernel. This means that if something is case sensitive on storage but case insensitive on lookup, an iteration using VOP_READDIR can get names that VOP_LOOKUP will be able to find, but that VOP_READDIR won't match, since the matching rules aren't applied in kernel space. This means that things like renames: touch foo fee mv foo Test mv fee test will fail to do the right thing. The only way you can really support case insensitivity on lookup is to move the globbing into the kernel, so that an iteration over the directory does the right thing. Or you could modify all your applications to treat such FSs differently. > > 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. The problem is that thee's really no way to support insensitive lookup correctly through the iterative interface, when doing globbing. It doesn't matter if your application is "ls" or it's "StarOffice". You would still need a contract between the case insensitive on lookup FS, and the code doing the globbing (in this case, in user space). > > 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). This is for the legacy stuff, not things like "Program Files". Windows 95's client will "fake up" case, if it's talking to a monocase server, by capitalizing the first letter. > 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). You might want to ask Jeremy Allison about this, I'm pretty sure he would know. It's probably a "feature" based on the protocol rev you are talking to the server. 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 Tue Oct 31 7:44:25 2000 Delivered-To: freebsd-fs@freebsd.org Received: from mail.over.ru (over.rinet.ru [195.54.192.99]) by hub.freebsd.org (Postfix) with SMTP id 4B29B37B4C5 for ; Tue, 31 Oct 2000 07:44:20 -0800 (PST) Received: (qmail 57908 invoked by uid 1001); 31 Oct 2000 15:44:07 -0000 Date: Tue, 31 Oct 2000 18:44:07 +0300 From: Alex Povolotsky To: Erez Zadok Cc: freebsd-fs@FreeBSD.ORG Subject: Re: crypto fs? Message-ID: <20001031184407.P81831@mail.over.ru> References: <200009280836.BAA11788@usr02.primenet.com> <200009291703.NAA29170@shekel.mcl.cs.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009291703.NAA29170@shekel.mcl.cs.columbia.edu>; from ezk@cs.columbia.edu on Fri, Sep 29, 2000 at 01:03:26PM -0400 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Sep 29, 2000 at 01:03:26PM -0400, Erez Zadok wrote: > Mine in the only known (so far :-) working stackable compression f/s. My > templates (Linux only) can do arbitrary size-changing f/s: I have a working > gzipfs, uuencodefs, etc. See http://www.cs.columbia.edu/~ezk/research/fist/ ... and what is with FreeBSD FiST? Does anyone working on it? Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 1 6:36: 3 2000 Delivered-To: freebsd-fs@freebsd.org Received: from mb1i0.ns.pitt.edu (mb1i0.ns.pitt.edu [136.142.186.35]) by hub.freebsd.org (Postfix) with ESMTP id 99CF137B479; Wed, 1 Nov 2000 06:35:59 -0800 (PST) Received: from pitt.edu ("port 1137"@[136.142.21.22]) by pitt.edu (PMDF V5.2-32 #41462) with ESMTP id <01JW0RUTGPZY004X8H@mb1i0.ns.pitt.edu>; Wed, 1 Nov 2000 09:35:26 EST Date: Wed, 01 Nov 2000 09:38:29 -0500 From: "Pedro F. Giffuni" Subject: Open AFS: Finally available !! To: freebsd-afs@FreeBSD.org Message-id: <3A002AE5.A76D5CF3@pitt.edu> Organization: University of Pittsburgh MIME-version: 1.0 X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Sony} (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en,pdf Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org http://oss.software.ibm.com/developerworks/opensource/afs/?dwzone=opensource To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 1 7:17:46 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 82DC837B479; Wed, 1 Nov 2000 07:17:42 -0800 (PST) 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 QAA07873; Wed, 1 Nov 2000 16:17:40 +0100 (CET) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id QAA02887; Wed, 1 Nov 2000 16:17:39 +0100 (CET) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 1 Nov 2000 16:17:39 +0100 (CET) From: Marius Bendiksen To: "Daniel C. Sobral" Cc: brueggma@snoopie.yi.org, freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: df -h In-Reply-To: <39FD097F.FCFDEF4A@newsguy.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 Daniel, the problem was solved using the output from this and another bug report a short while ago. Boris is the one who was spending the time on it, so please don't get this upset. The "after X minutes" clue was actually the most relevant bit, as NT tends to drop all SMB mounts after a short period of inactivity. Windows reconnects automatically. Most people who have tried sharity-light, for example, will have seen this already. --- Marius Bendiksen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 1 10:35:38 2000 Delivered-To: freebsd-fs@freebsd.org Received: from pedigree.cs.ubc.ca (pedigree.cs.ubc.ca [142.103.6.50]) by hub.freebsd.org (Postfix) with ESMTP id E7DEB37B4C5 for ; Wed, 1 Nov 2000 10:35:35 -0800 (PST) Received: from cascade.cs.ubc.ca (dima@cascade.cs.ubc.ca [142.103.7.7]) by pedigree.cs.ubc.ca (8.8.8/8.6.9) with ESMTP id KAA06737 for ; Wed, 1 Nov 2000 10:35:28 -0800 (PST) From: Dmitry Brodsky Received: (dima@localhost) by cascade.cs.ubc.ca (8.9.3/8.6.12) id KAA04865 for freebsd-fs@freebsd.org; Wed, 1 Nov 2000 10:35:27 -0800 (PST) Message-Id: <200011011835.KAA04865@cascade.cs.ubc.ca> Subject: Hiding the lower layer in a stackable FS To: freebsd-fs@freebsd.org Date: Wed, 1 Nov 2000 10:35:27 -0800 (PST) X-Mailer: ELM [version 2.5 PL3] 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 Hi, I am wondering if it is possible to hide the underlying filesystem in a stackable filesystem configureation. For example. In the nullfs example you would do the following to mount it: mount /dev/adXsYZ mntpoint (UFS fs) mount -t nullfs mntpoint nullfs_mntpoint (NULL fs) Now both mntpoint and nullfs_mntpoint is visible to the user. Ideally what I would like to do is have the user enter mount -t nullfs /dev/adXsYZ nullfs_mntpoint (UFS fs) and have them see only the nullfs mntpoint rather than both mntpoint and nullfs_mntpoint. Is this possible??? I would still like the underlying FS to be UFS. Thanks ttyl Dima -- Dima Brodsky dima@cs.ubc.ca http://www.cs.ubc.ca/~dima 201-2366 Main Mall (604) 822-6179 (Office) Department of Computer Science (604) 822-2895 (DSG Lab) University of British Columbia, Canada (604) 822-5485 (FAX) Computers are like Old Testament gods; lots of rules and no mercy. (Joseph Campbell) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 1 15: 9:12 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 C9F8737B4F9 for ; Wed, 1 Nov 2000 15:09:09 -0800 (PST) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id QAA17654; Wed, 1 Nov 2000 16:09:39 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp05.primenet.com, id smtpdAAAf0aWyI; Wed Nov 1 16:09:27 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id QAA06107; Wed, 1 Nov 2000 16:08:51 -0700 (MST) From: Terry Lambert Message-Id: <200011012308.QAA06107@usr08.primenet.com> Subject: Re: Hiding the lower layer in a stackable FS To: dima@cs.ubc.ca (Dmitry Brodsky) Date: Wed, 1 Nov 2000 23:08:51 +0000 (GMT) Cc: freebsd-fs@FreeBSD.ORG In-Reply-To: <200011011835.KAA04865@cascade.cs.ubc.ca> from "Dmitry Brodsky" at Nov 01, 2000 10:35:27 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 > I am wondering if it is possible to hide the underlying filesystem > in a stackable filesystem configureation. [ ... ] Yes. This is the intended behaviour, and is how it works. It would not be useful to expose, for example, a namespace translation layer contents, if the untranslated contents were not useful. For example, a stacking layer that supported multiple versions of files might be implemented so that it used different names for different versions, and these names would not necessarily be useful, or might in fact be confusing, were they exposed to the user. Likewise, it's not a good idea (even though the integral code in UFS currently does this) to expose the quota file, where it could be tampered with or otherwise cause an FS with quotas enabled to lock up on you. 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 Wed Nov 1 17:25:39 2000 Delivered-To: freebsd-fs@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C4B0337B4F9; Wed, 1 Nov 2000 17:25:35 -0800 (PST) Received: from newsguy.com (p09-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.138]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id KAA25262; Thu, 2 Nov 2000 10:25:25 +0900 (JST) Message-ID: <3A00C227.520EDB7E@newsguy.com> Date: Thu, 02 Nov 2000 10:23:51 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Marius Bendiksen Cc: brueggma@snoopie.yi.org, freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: df -h References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marius Bendiksen wrote: > > Daniel, the problem was solved using the output from this and another bug > report a short while ago. Boris is the one who was spending the time on > it, so please don't get this upset. The "after X minutes" clue was > actually the most relevant bit, as NT tends to drop all SMB mounts after a > short period of inactivity. Windows reconnects automatically. Most people > who have tried sharity-light, for example, will have seen this already. I'm not getting upset. I'm pointing out what kind of problem report is unlikely to see results, and what kind does. I'm happy the problem was solved, I'm glad the information provided was enough, but the general point I made is still valid. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@world.wide.bsdconspiracy.net He has been convicted of criminal possession of a clue with intent to distribute. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Nov 1 21: 1:13 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 DD07137B4C5 for ; Wed, 1 Nov 2000 21:01:11 -0800 (PST) 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 AAA11430; Thu, 2 Nov 2000 00:01:09 -0500 (EST) Received: (from ezk@localhost) by shekel.mcl.cs.columbia.edu (8.9.3/8.9.3) id AAA11555; Thu, 2 Nov 2000 00:01:09 -0500 (EST) Date: Thu, 2 Nov 2000 00:01:09 -0500 (EST) Message-Id: <200011020501.AAA11555@shekel.mcl.cs.columbia.edu> From: Erez Zadok To: Alex Povolotsky Cc: Erez Zadok , freebsd-fs@FreeBSD.ORG Subject: Re: crypto fs? In-reply-to: Your message of "Tue, 31 Oct 2000 18:44:07 +0300." <20001031184407.P81831@mail.over.ru> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20001031184407.P81831@mail.over.ru>, Alex Povolotsky writes: > On Fri, Sep 29, 2000 at 01:03:26PM -0400, Erez Zadok wrote: > > Mine in the only known (so far :-) working stackable compression f/s. My > > templates (Linux only) can do arbitrary size-changing f/s: I have a working > > gzipfs, uuencodefs, etc. See http://www.cs.columbia.edu/~ezk/research/fist/ > ... and what is with FreeBSD FiST? Does anyone working on it? > > Alex. It's been working as of 3.3, but with my stacking template that had to work around the VFS problems. Certainly cryptfs is working. I've not done a full port using the latest nullfs yet, which, I understand uses the fixed VFS. Erez. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Nov 2 7: 1: 4 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 5445637B4CF for ; Thu, 2 Nov 2000 07:01:01 -0800 (PST) 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 QAA65867; Thu, 2 Nov 2000 16:00:57 +0100 (CET) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id QAA10271; Thu, 2 Nov 2000 16:00:57 +0100 (CET) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Thu, 2 Nov 2000 16:00:56 +0100 (CET) From: Marius Bendiksen To: Dmitry Brodsky Cc: freebsd-fs@freebsd.org Subject: Re: Hiding the lower layer in a stackable FS In-Reply-To: <200011011835.KAA04865@cascade.cs.ubc.ca> 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 > Is this possible??? I would still like the underlying FS to be UFS. If I understand you correctly, then I think you could do something like this: bzero( nullmp->mnt_stat.f_mntfromname, MNAMELEN ); copystr( realmp->mnt_stat.f_mntfromname, nullmp->mnt_stat.f_mntfromname, MNAMELEN - 1, &size ); That would provide a fake mount-from value. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Nov 2 9:18:28 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 B583937B4C5 for ; Thu, 2 Nov 2000 09:18:26 -0800 (PST) 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 MAA28392 for ; Thu, 2 Nov 2000 12:18:21 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 2 Nov 2000 12:18:20 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-fs@FreeBSD.org Subject: got bad cookie vp 0xc8af0000 bp 0xc36ac220 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 Never got that message from NFS before -- this is with two 5-CURRENT boxes, one from a month or so ago, the other from yesterday. Is this something I should be worried about, or a sign of a stateless network file system at work? Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message