From owner-freebsd-fs Sun Oct 7 19:38:17 2001 Delivered-To: freebsd-fs@freebsd.org Received: from smail-103.hanmail.net (smail-103.hanmail.net [211.233.29.58]) by hub.freebsd.org (Postfix) with ESMTP id C3AAB37B403 for ; Sun, 7 Oct 2001 19:38:13 -0700 (PDT) Received: from www15.hanmail.net (www15.hanmail.net [211.32.117.35]) by smail-103.hanmail.net (8.10.0/8.9.1) with ESMTP id f982VE827465; Mon, 8 Oct 2001 11:31:14 +0900 Received: (from hanadmin@localhost) by www15.hanmail.net (8.10.0/8.9.1) id f982ThM14200 for ; Mon, 8 Oct 2001 11:29:43 +0900 (KST) X-Originating-IP: [129.254.122.173] From: "=?EUC-KR?B?wNPA57T2?=" Reply-To: "=?EUC-KR?B?wNPA57T2?=" Organization: =?EUC-KR?B?sOa6z7Trx9Cxsw==?= To: Subject: about vnode operations... X-Mailer: Daum Web Mailer 1.0 Date: Mon, 08 Oct 2001 11:29:43 +0900 (KST) Message-Id: <20011008112943.HM.E0000000002RpGO@www15.hanmail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 8bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, everyone.. I have some questions with tracing the kernel source code about file system in FreeBSD 4.3. I read book, 'The Design and Inplementation of the 4.4BSD Operation System', but I can't underatand them. Please tell me the fellowing questions. There are many operations starting with vn_*** and VOP_***. I don't know the the main difference between the two. What is the main difference between the two. And if i want to add new operations in the exist file system as a vnode operations, What can i do for it? How are the vnode operations created and worked when system is started..?? I found 'vnode_if.src' file in /sys/kern/ directory. I think that this file is played a some role in vnode operations. Right..?? Please teach me above questions... Thank you in advance.. Have a good day. =================================================================== 우리 인터넷, Daum http://www.daum.net 화끈한 원샷 검색! Daum검색 쿠치로 찾자! ☞검색하기 http://search.daum.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Oct 7 21:52:12 2001 Delivered-To: freebsd-fs@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id 8A59F37B403 for ; Sun, 7 Oct 2001 21:52:06 -0700 (PDT) Received: from mindspring.com (dialup-209.247.143.125.Dial1.SanJose1.Level3.net [209.247.143.125]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f984q2921648; Sun, 7 Oct 2001 21:52:02 -0700 (PDT) Message-ID: <3BC13124.5655F3D7@mindspring.com> Date: Sun, 07 Oct 2001 21:52:52 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?=C0=D3=C0=E7=B4=F6?= Cc: freebsd-fs@freebsd.org Subject: Re: about vnode operations... References: <20011008112943.HM.E0000000002RpGO@www15.hanmail.net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org =C0=D3=C0=E7=B4=F6 wrote: > = > Hello, everyone.. > I have some questions with tracing the kernel source code about > file system in FreeBSD 4.3. OK. > I read book, 'The Design and Inplementation of the 4.4BSD Operation > System', but I can't underatand them. The book is not entirely accurate, with regards to FreeBSD; there is another book rumored to be in the works that is specifically geared to FreeBSD. > Please tell me the fellowing questions. > = > There are many operations starting with vn_*** and VOP_***. > I don't know the the main difference between the two. > What is the main difference between the two. VOP operations are descriptor based argument list functions which are generic, and are epxted to be implemented by each VFS top operate on files within the file system. The vn operations are implementations above the VFS layer, but below the system call layer, for common operations at the system call layer. They can also be abused to do file I/O within the kernel, if they are used exactly right. A better interface for this would pass a UIO_USRSPACE or a UIO_SYSSPACE argument, and the code woul Just Work(tm) in the kernel. Reading the source code would probably be helpful for you. In general, the VOP operations are not called until a file system is mounted (via VFS operations). If you consider this from the file descriptor perspective, the VOP operations are those which are called as a result of the struct fileops in a file descriptor pointing to the vfsops version of the structure. > And if i want to add new operations in the exist file system > as a vnode operations, What can i do for it? You define the operations in the vnode_if.src in /sys/kern, and the vnode_if.c and vnode_if.h are created when you do the kernel compilation. In general, you will need to supply new system calls to call the new VOP's to actually implement calls to your new code, within a VFS. > How are the vnode operations created and worked when system > is started..?? You can't do this after the system is started. The problem is that the descriptor structure used for the lookups is created at kernel compilation time, and can not be recreated; there are three barries to adding new VOPs to the list of allowable VOPs for all VFSs: 1) The already instanced VFSs will not have these VOPs in their table, and the defaultops which things fall through to will cause this to break if you call the system call that calls the new VOP on an FS that was instanced before the VFS con taining the new VOP was loaded. The way to fix this is to refactor the VFS VOP vectors each time a new VOP is added to the system. For this to work, the VOP vector list _must_ be sorted. If it is sorted, you get the advantage of being able to use a direct index at instancing time, so that the reverse lookup for the vector is avoided. This can also improve VFS interface speed significantly, so it's worthwhile to do in its own right. 2) The new VOPs will not be in the global descriptor table from the vnode_if.c. The way to fix this is to change references to this to a pointer, allocate the data at runtime, and then do a reallocation each time a new VOP comes along. 3) Collisions. If you add VOPs by index, you rin the risk of using the same index as another VOP added by another VFS. The fix for this is to add a third field, a string name, and to use the string name to add the operation. You will still run the (lesser) risk of having a namespace collision (e.g. if two FS's want to add an "abort", and each "abort" has differing semantics), but the alternative is a seperate system call per VFS per new VOP. > I found 'vnode_if.src' file in /sys/kern/ directory. > I think that this file is played a some role in vnode operations. > Right..?? Yes. > Please teach me above questions... If you could tell us *why* you wanted to know, we could probably give you more domain specific answers, which would cut the number and generality of the questions you will have to ask to get your code working. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Oct 8 21:39:52 2001 Delivered-To: freebsd-fs@freebsd.org Received: from smtp.whitebarn.com (Spin.whitebarn.com [216.0.13.113]) by hub.freebsd.org (Postfix) with ESMTP id 7709037B401; Mon, 8 Oct 2001 21:39:40 -0700 (PDT) Received: from BGPBook.Com (Relent.Bob.whitebarn.com [216.0.13.50]) by smtp.whitebarn.com (8.9.3/8.9.3) with ESMTP id XAA34553; Mon, 8 Oct 2001 23:39:38 -0500 (CDT) (envelope-from Bob@BGPBook.Com) Message-ID: <3BC27F89.4090706@BGPBook.Com> Date: Mon, 08 Oct 2001 23:39:37 -0500 From: Bob Van Valzah User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: FreeBSD-Hardware@FreeBSD.Org, FreeBSD-SCSI@FreeBSD.Org, FreeBSD-Install@FreeBSD.Org, FreeBSD-FS@FreeBSD.Org, FreeBSD-Hackers@FreeBSD.Org, FreeBSD-Config@FreeBSD.Org Subject: Vinum Bootstrapping Article Reviewers Wanted Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm working on an article that describes how to get started using Vinum (software RAID). After a gentle introduction, it takes the reader through the process starting with /stand/sysinstall and ending with a sever with mirrored volumes. It also covers several hardware failure scenarios and the recovery techniques needed to get a server back to normal. I'd like to make sure that the step-by-step procedures that it contains are correct for a wide audience. Folks experienced with Vinum could help by reviewing the article and commenting on subtleties I've missed. Vinum newbies could by providing a perspective that I lack. I'd particularly like to find reviewers who tried to get Vinum going in the past but gave up. You'll need to have access to a CPU on which you can do fresh FreeBSD installs. Anything better than a 486 with 8 MB of RAM should be ok as long as you can get to installation media. You'll need two or more disk drives of at least 500 MB or so. IDE or SCSI, mix & match are ok. The article is about 30 pages, so you'll need time to read it and try the procedures. I'd budget at least 2-3 hours, more if you'll have to scrape the hardware together. Comments returned to me in the next few days might make it into a version of the article that I hope will appear in the next print edition of the handbook. So if you have the necessary time, hardware, and inclination, please drop me a line and I'll get you a draft! Thanks, Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 9 4:10: 3 2001 Delivered-To: freebsd-fs@freebsd.org Received: from stiggy.masaclaw.co.nz (203-79-83-205.cable.paradise.net.nz [203.79.83.205]) by hub.freebsd.org (Postfix) with ESMTP id 6982737B401 for ; Tue, 9 Oct 2001 04:09:58 -0700 (PDT) Received: from there (unknown [192.168.0.80]) by stiggy.masaclaw.co.nz (Postfix) with SMTP id 99429505 for ; Tue, 9 Oct 2001 12:12:40 +1300 (NZDT) Content-Type: text/plain; charset="iso-8859-1" From: Tom Peck To: freebsd-fs@freebsd.org Subject: NFS sharing an NFS Mount Date: Wed, 10 Oct 2001 00:07:58 +1300 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011008231240.99429505@stiggy.masaclaw.co.nz> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi Is it possible to nfs share a mount that has been mounted using nfs? Here's my setup.. I have one system which holds files, which is shared using nfs. I have another system which mounts this nfs share from the other system. This share then needs to be shared from the second system to all other available systems.. I have tried without success to let this happen. How can this nfs mount be added to the /etc/fstab file? I assume it has to be before the /etc/exports file has been read.. Thanks for any help.. i'm new to this game.. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 9 11:44: 7 2001 Delivered-To: freebsd-fs@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 6858D37B40A for ; Tue, 9 Oct 2001 11:44:04 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id f99IiFq98079; Tue, 9 Oct 2001 11:44:15 -0700 (PDT) Date: Tue, 9 Oct 2001 11:44:14 -0700 (PDT) From: Doug White To: Tom Peck Cc: Subject: Re: NFS sharing an NFS Mount In-Reply-To: <20011008231240.99429505@stiggy.masaclaw.co.nz> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 10 Oct 2001, Tom Peck wrote: > Is it possible to nfs share a mount that has been mounted using nfs? No. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Tue Oct 9 12:33: 7 2001 Delivered-To: freebsd-fs@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 217EC37B408 for ; Tue, 9 Oct 2001 12:33:04 -0700 (PDT) Received: from mindspring.com (dialup-209.247.137.25.Dial1.SanJose1.Level3.net [209.247.137.25]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id MAA08875; Tue, 9 Oct 2001 12:32:57 -0700 (PDT) Message-ID: <3BC3511C.736F595A@mindspring.com> Date: Tue, 09 Oct 2001 12:33:48 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Tom Peck Cc: freebsd-fs@freebsd.org Subject: Re: NFS sharing an NFS Mount References: <20011008231240.99429505@stiggy.masaclaw.co.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Tom Peck wrote: > Is it possible to nfs share a mount that has been mounted using nfs? Not without violating safety guarantees in the protocol as regars not returning writes until they have been committed to stable storage. > I have one system which holds files, which is shared using nfs. I have > another system which mounts this nfs share from the other system. This share > then needs to be shared from the second system to all other available > systems.. You can't do this. It sounds like you need a VPN, or to simply have all the other systems mount the first one. > I have tried without success to let this happen. How can this nfs > mount be added to the /etc/fstab file? I assume it has to be before > the /etc/exports file has been read.. You can't do this because the NFS code will not permit it to happen. By the same token, you do not want to mix any other network FS with more than one hop (SMBFS, NWFS, AFS, AppleTalk, etc.). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 9 12:48: 2 2001 Delivered-To: freebsd-fs@freebsd.org Received: from localnet.sh (www.localnet.sh [216.40.195.67]) by hub.freebsd.org (Postfix) with ESMTP id 23C8A37B406 for ; Tue, 9 Oct 2001 12:47:59 -0700 (PDT) Received: (from offe@localhost) by localnet.sh (8.10.2/8.10.2) id f99JisY18618; Tue, 9 Oct 2001 14:44:54 -0500 Date: Tue, 9 Oct 2001 14:44:54 -0500 From: Olof Johansson Message-Id: <200110091944.f99JisY18618@localnet.sh> To: tlambert2@mindspring.com Cc: freebsd-fs@freebsd.org Subject: Re: NFS sharing an NFS Mount In-Reply-To: <3BC3511C.736F595A@mindspring.com> References: <20011008231240.99429505@stiggy.masaclaw.co.nz> <3BC3511C.736F595A@mindspring.com> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In muc.lists.freebsd.fs, you wrote: >Tom Peck wrote: >> Is it possible to nfs share a mount that has been mounted using nfs? > >Not without violating safety guarantees in the protocol as >regars not returning writes until they have been committed >to stable storage. Not entirely true. NFS version 3 has the option of unstable writes, which are usually used by the ONC+-derived clients (Solaris, AIX, ...). On the other hand, then the commit calls must not return until the data is on stable storage. Also, one could technically write a NFS gateway that simply relays the RPC calls and makes sure they are not returned to the "real" client until a reply has been received from the server. However, I am not aware of any such gateway in existance. Regards, Olof To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Tue Oct 9 12:50:53 2001 Delivered-To: freebsd-fs@freebsd.org Received: from stiggy.masaclaw.co.nz (203-79-83-205.cable.paradise.net.nz [203.79.83.205]) by hub.freebsd.org (Postfix) with ESMTP id 4B46B37B408 for ; Tue, 9 Oct 2001 12:50:50 -0700 (PDT) Received: from there (unknown [192.168.0.80]) by stiggy.masaclaw.co.nz (Postfix) with SMTP id 4976B505 for ; Tue, 9 Oct 2001 20:53:32 +1300 (NZDT) Content-Type: text/plain; charset="iso-8859-1" From: Tom Peck To: freebsd-fs@freebsd.org Subject: Re: NFS sharing an NFS Mount Date: Wed, 10 Oct 2001 08:48:51 +1300 X-Mailer: KMail [version 1.3] References: <20011008231240.99429505@stiggy.masaclaw.co.nz> <3BC3511C.736F595A@mindspring.com> In-Reply-To: <3BC3511C.736F595A@mindspring.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011009075332.4976B505@stiggy.masaclaw.co.nz> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ok. Thanks for the explanation. I will have to think about an alternative solution. Cheers Tom On Wed, 10 Oct 2001 08:33, Terry Lambert spoke unto bla: > Tom Peck wrote: > > Is it possible to nfs share a mount that has been mounted using nfs? > > Not without violating safety guarantees in the protocol as > regars not returning writes until they have been committed > to stable storage. > > > I have one system which holds files, which is shared using nfs. I have > > another system which mounts this nfs share from the other system. This > > share then needs to be shared from the second system to all other > > available systems.. > > You can't do this. It sounds like you need a VPN, or to > simply have all the other systems mount the first one. > > > I have tried without success to let this happen. How can this nfs > > mount be added to the /etc/fstab file? I assume it has to be before > > the /etc/exports file has been read.. > > You can't do this because the NFS code will not permit it > to happen. > > By the same token, you do not want to mix any other network > FS with more than one hop (SMBFS, NWFS, AFS, AppleTalk, etc.). > > -- Terry > > 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 Tue Oct 9 14:53:50 2001 Delivered-To: freebsd-fs@freebsd.org Received: from wg.pu.ru (wg.pu.ru [193.124.85.219]) by hub.freebsd.org (Postfix) with ESMTP id B3BFA37B409 for ; Tue, 9 Oct 2001 14:53:46 -0700 (PDT) Received: from YB3791.UUCP (uucp@localhost) by wg.pu.ru (8.9.1a/8.9.1) with UUCP id VAA21388 for freebsd-fs@freebsd.org; Tue, 9 Oct 2001 21:53:45 GMT Received: by YB3791.spb.edu (UUPC/@ v7.02, 01May98) id AA00148; Wed, 10 Oct 2001 01:52:59 +0400 (MSD) From: "Yan V. Batuto" To: "freebsd-fs@freebsd.org" Date: Wed, 10 Oct 2001 01:52:57 +0400 (MSD) Reply-To: "Yan V. Batuto" X-Mailer: PMMail 2.20.2200 for OS/2 Warp 4.00 MIME-Version: 1.0 Subject: smbfs troubles Message-Id: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Lines: 23 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! I noticed a strange smbfs behaviour. It never shows more than 50 filenames in a directory. (Sorry, I forget a '.' and '..', so "no more than 52 filenames".) However I can access any file which is not shown, but really exists on the server. For example, I can cd to any unlisted catalog and look to its content... It looks like findnext_smbfs function gets from somewhere a small limit for number of files. On the other hand, ftp-like smbclient shows right all directory content (from the same server) regardless of its size. Server is living under OS/2 Warp 4.5. Client is FreeBSD 4.4-release (but no differences in comparision with 4.3). What can I do to see all files? Yan V. Batuto To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Oct 10 11:27:14 2001 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 C38A837B401 for ; Wed, 10 Oct 2001 11:27:11 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9AIQpB58625; Wed, 10 Oct 2001 14:26:51 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 10 Oct 2001 14:26:50 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dag-Erling Smorgrav Cc: "David E. Cross" , freebsd-fs@FreeBSD.ORG Subject: Re: OpenAFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 6 Oct 2001, Dag-Erling Smorgrav wrote: > Robert Watson writes: > > The man pages are not known either for their technical depth, nor (it > > turns out) their correctness. Likewise, the locking statements in > > vnode_if.src were fairly out of sync last I checked. If that's changed, > > and I'm simply dated, I'm delighted to hear that :-). > > Eivind worked very hard to update them a few years ago (when he rewrote > vnode_if.pl from Bourne shell to Perl), and AFAIK they haven't been > subject to change since then. I might be wrong, but I doubt it. It has improved a fair amount from what I remember being there, but the VFS man pages are still quite out of sync. Also, vop_getattr is still recorded as not requiring a lock on the vnode whereas most invocations I've seen do grab the lock. I've often wondered if (in our current locking scheme) in practice it shouldn't be marked as L L L. Also, vnode_if.src helpfully lists a number of possible locking modes that are never used (and that locking scheme isn't designed for) such as shared locking. Some of that should probably be trimmed so as not to be misleading. 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 From owner-freebsd-fs Wed Oct 10 13: 5:55 2001 Delivered-To: freebsd-fs@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 6A5C837B401; Wed, 10 Oct 2001 13:05:52 -0700 (PDT) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA00513; Wed, 10 Oct 2001 16:05:45 -0400 (EDT) Message-Id: <200110102005.QAA00513@cs.rpi.edu> To: Robert Watson Cc: Dag-Erling Smorgrav , "David E. Cross" , freebsd-fs@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: OpenAFS In-Reply-To: Message from Robert Watson of "Wed, 10 Oct 2001 14:26:50 EDT." Date: Wed, 10 Oct 2001 16:05:45 -0400 From: "David E. Cross" Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I think for my first FS coding project I will attempt to write the "ProDOS" apple 2 filesystem. Why? I know it very well. Perhaps from that I can write an introduction to filesystems for FreeBSD (maybe :) -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Oct 10 13:13:51 2001 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 7786937B401 for ; Wed, 10 Oct 2001 13:13:48 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9AKDZB60118; Wed, 10 Oct 2001 16:13:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 10 Oct 2001 16:13:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "David E. Cross" Cc: Dag-Erling Smorgrav , freebsd-fs@FreeBSD.ORG Subject: Re: OpenAFS In-Reply-To: <200110102005.QAA00513@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 10 Oct 2001, David E. Cross wrote: > I think for my first FS coding project I will attempt to write the > "ProDOS" apple 2 filesystem. Why? I know it very well. Perhaps from > that I can write an introduction to filesystems for FreeBSD (maybe :) Well, if you're going the Apple route, how about your second fs project be porting HFS+ to FreeBSD, and documenting the differences in VFS between the two + implications? :-) 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 From owner-freebsd-fs Wed Oct 10 13:15:16 2001 Delivered-To: freebsd-fs@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 88E1137B405; Wed, 10 Oct 2001 13:15:13 -0700 (PDT) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA00839; Wed, 10 Oct 2001 16:15:11 -0400 (EDT) Message-Id: <200110102015.QAA00839@cs.rpi.edu> To: Robert Watson Cc: "David E. Cross" , Dag-Erling Smorgrav , freebsd-fs@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: OpenAFS In-Reply-To: Message from Robert Watson of "Wed, 10 Oct 2001 16:13:35 EDT." Date: Wed, 10 Oct 2001 16:15:11 -0400 From: "David E. Cross" Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hahahhahahahah *breath* Hahahahaha... I don't know HFS/HFS+ _at_all_. This project was so that I only tackled one unknown (the VFS layer). -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Wed Oct 10 13:17:23 2001 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 9A55A37B406 for ; Wed, 10 Oct 2001 13:17:20 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f9AKHFB60159; Wed, 10 Oct 2001 16:17:15 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 10 Oct 2001 16:17:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "David E. Cross" Cc: Dag-Erling Smorgrav , freebsd-fs@FreeBSD.ORG Subject: Re: OpenAFS In-Reply-To: <200110102015.QAA00839@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 10 Oct 2001, David E. Cross wrote: > Hahahhahahahah *breath* Hahahahaha... The great thing about FreeBSD as a passtime is how much entertainment it can provide :-). > I don't know HFS/HFS+ _at_all_. This project was so that I only tackled > one unknown (the VFS layer). It probably won't be too hard. You might find the MSDOSfs code a good place to start looking. 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 From owner-freebsd-fs Fri Oct 12 20:47:55 2001 Delivered-To: freebsd-fs@freebsd.org Received: from boomerang.bytehosting.com (boomerang.bytehosting.com [65.196.231.162]) by hub.freebsd.org (Postfix) with SMTP id 6615737B40A for ; Fri, 12 Oct 2001 20:47:46 -0700 (PDT) Received: (qmail 24264 invoked by uid 0); 13 Oct 2001 01:40:07 -0000 Received: from rob@thechain.com by boomerang.bytehosting.com with qmail-scanner-0.96 (sweep: 2.4/3.47. . Clean. Processed in 0.700134 secs); 13 Oct 2001 01:40:07 -0000 X-Qmail-Scanner-Mail-From: rob@thechain.com via boomerang.bytehosting.com X-Qmail-Scanner: 0.96 (No viruses found. Processed in 0.700134 secs) Received: from unknown (HELO winbox) (@24.2.78.52) by mail.thechain.com with SMTP; 13 Oct 2001 01:40:06 -0000 From: "Rob" To: , Subject: Boot error.. Corrupted file system? Date: Fri, 12 Oct 2001 23:40:55 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: Importance: Normal Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I am writing this mailing list in a desperate attempt to find out how to restore my hdd with out loosing all the data on it. Recently I added two additional hard drives to my freebsd 4.2 system. Once I booted up my system and dl'ed some things with wget a bunch of errors occurred resulting in "kernel panic" and then system halt. When I rebooted I get and error and cannot boot freebsd error: Verifying DMI Pool Data ......... | int=00000000 err=00000000 efl=00010246 eip=00001b2c eax=00000002 ebx=00000002 ecx=00006564 edx=00000000 esi=00094cdc edi=000022bf ebp=00094cbc esp=00094ca4 cs=002b ds=0033 es=0033 fs=0033 gs=0033 gs=0033 ss=0033 cs:eip=f7 35 98 24 00 00 89 c7-89 f9 0f af 0d 9c 24 00 ss:esp=00 00 00 00 e0 4c 09 00-dc 4c 09 00 bf 22 00 00 BTX halted to try to fix this problem I installed a minimal install of fbsd on another hdd and ran fsck /dev/ad1a which said this: ** /dev/ad1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/ad1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 9809920 Although it doesn't really help I can still df -h it; df /dev/ad1a prints: Filesystem Size Used Avail Capacity Mounted on /dev/ad1a 4.5G 1.5G 2.7G 36% fdisk /dev/ad1a prints: *****Working on device /dev/ad1a ********* parameters extracted from in-core disklabel are: cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calclations are: cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end:cyl 1023/ head 255/ sector 63 Is the data on my hdd completely unrecoverable? Is there anyway I could mount the partion? mount /dev/ad1a /blah (/blah is a directory) prints this: mount: /dev/ad1a on /blah: incorrect super block To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Oct 12 20:51: 4 2001 Delivered-To: freebsd-fs@freebsd.org Received: from boomerang.bytehosting.com (boomerang.bytehosting.com [65.196.231.162]) by hub.freebsd.org (Postfix) with SMTP id E04CE37B40C for ; Fri, 12 Oct 2001 20:50:53 -0700 (PDT) Received: (qmail 24393 invoked by uid 0); 13 Oct 2001 01:43:19 -0000 Received: from rob@thechain.com by boomerang.bytehosting.com with qmail-scanner-0.96 (sweep: 2.4/3.47. . Clean. Processed in 0.858127 secs); 13 Oct 2001 01:43:19 -0000 X-Qmail-Scanner-Mail-From: rob@thechain.com via boomerang.bytehosting.com X-Qmail-Scanner: 0.96 (No viruses found. Processed in 0.858127 secs) Received: from unknown (HELO winbox) (@24.2.78.52) by mail.thechain.com with SMTP; 13 Oct 2001 01:43:18 -0000 From: "Rob" To: "Rob" , , Subject: RE: Boot error.. Corrupted file system? Date: Fri, 12 Oct 2001 23:44:06 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: Importance: Normal Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org err sorry didn't meen for multiple sends -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Rob Sent: Friday, October 12, 2001 11:41 PM To: freebsd-fs@FreeBSD.ORG; questions@freebsd.org Subject: Boot error.. Corrupted file system? I am writing this mailing list in a desperate attempt to find out how to restore my hdd with out loosing all the data on it. Recently I added two additional hard drives to my freebsd 4.2 system. Once I booted up my system and dl'ed some things with wget a bunch of errors occurred resulting in "kernel panic" and then system halt. When I rebooted I get and error and cannot boot freebsd error: Verifying DMI Pool Data ......... | int=00000000 err=00000000 efl=00010246 eip=00001b2c eax=00000002 ebx=00000002 ecx=00006564 edx=00000000 esi=00094cdc edi=000022bf ebp=00094cbc esp=00094ca4 cs=002b ds=0033 es=0033 fs=0033 gs=0033 gs=0033 ss=0033 cs:eip=f7 35 98 24 00 00 89 c7-89 f9 0f af 0d 9c 24 00 ss:esp=00 00 00 00 e0 4c 09 00-dc 4c 09 00 bf 22 00 00 BTX halted to try to fix this problem I installed a minimal install of fbsd on another hdd and ran fsck /dev/ad1a which said this: ** /dev/ad1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/ad1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 9809920 Although it doesn't really help I can still df -h it; df /dev/ad1a prints: Filesystem Size Used Avail Capacity Mounted on /dev/ad1a 4.5G 1.5G 2.7G 36% fdisk /dev/ad1a prints: *****Working on device /dev/ad1a ********* parameters extracted from in-core disklabel are: cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calclations are: cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end:cyl 1023/ head 255/ sector 63 Is the data on my hdd completely unrecoverable? Is there anyway I could mount the partion? mount /dev/ad1a /blah (/blah is a directory) prints this: mount: /dev/ad1a on /blah: incorrect super block 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