From owner-freebsd-fs@FreeBSD.ORG Fri Jul 2 18:42:39 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9491816A4CE for ; Fri, 2 Jul 2004 18:42:39 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AB8F43D41 for ; Fri, 2 Jul 2004 18:42:39 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id C2EC35C856; Fri, 2 Jul 2004 11:40:20 -0700 (PDT) Date: Fri, 2 Jul 2004 11:40:20 -0700 From: Alfred Perlstein To: fs@freebsd.org Message-ID: <20040702184020.GC95729@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: tweaking mounted filesystems by fsid X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2004 18:42:39 -0000 Hi. The last year or so I spent bringing file system improvements into OS X. The mechanism I used to tweak filesystems was sysctl. I created a node that would route a request to a filesystem based on a fsid. This would allow tweaking of filesystems without entering the namespace. I realize we have the nmount syscall. I have several questions about it. 1) can I muck with it so that it functions like unmount(2) by taking the "FSID:val0:val1" parameter in order to properly route requests? 2) what if i want to pass binary data? I can do that right? I assume by just passing the binary gook via the value of the key value pair. Any comments? On of the issues I have is that I need the call to be callable from both inside and outside of the kernel, I'm guessing this can be taken care of by the internal options... Ideas people? Use nmount or sysctl? FYI, the stuff that depends on this is filesystem mobility, filesystem notifications and autofs. -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684 From owner-freebsd-fs@FreeBSD.ORG Fri Jul 2 19:29:41 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC42416A4CE for ; Fri, 2 Jul 2004 19:29:41 +0000 (GMT) Received: from web13123.mail.yahoo.com (web13123.mail.yahoo.com [216.136.174.141]) by mx1.FreeBSD.org (Postfix) with SMTP id 9CF1543D2F for ; Fri, 2 Jul 2004 19:29:41 +0000 (GMT) (envelope-from k_tutorials@yahoo.com) Message-ID: <20040702192845.79255.qmail@web13123.mail.yahoo.com> Received: from [209.213.198.25] by web13123.mail.yahoo.com via HTTP; Fri, 02 Jul 2004 12:28:45 PDT Date: Fri, 2 Jul 2004 12:28:45 -0700 (PDT) From: Krishna Monian To: fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Getting the complete path for a file X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2004 19:29:41 -0000 Hi All, I am in the process of writing a file logging utility. I am going about doing this by rerouting vfs system calls, and logging the information needed. However I am facing the following problem. When files are accessed through the terminal, relative paths are used as opposed to complete paths. Is there any way that I can reconstruct the complete path, given that I have access to all the information that is normally passed to the vfs system calls. Thanks Krishna __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail From owner-freebsd-fs@FreeBSD.ORG Sat Jul 3 19:49:39 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97CA616A4CE; Sat, 3 Jul 2004 19:49:39 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121FC43D48; Sat, 3 Jul 2004 19:49:39 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.0.12] (g4.samsco.home [192.168.0.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i63Js1VV083254; Sat, 3 Jul 2004 13:54:01 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <40E70D90.4090304@freebsd.org> Date: Sat, 03 Jul 2004 13:48:32 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alfred Perlstein References: <20040702184020.GC95729@elvis.mu.org> In-Reply-To: <20040702184020.GC95729@elvis.mu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: fs@freebsd.org Subject: Re: tweaking mounted filesystems by fsid X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 19:49:39 -0000 Alfred Perlstein wrote: > Hi. > > The last year or so I spent bringing file system improvements into > OS X. > > The mechanism I used to tweak filesystems was sysctl. > > I created a node that would route a request to a filesystem based > on a fsid. This would allow tweaking of filesystems without entering > the namespace. > > I realize we have the nmount syscall. I have several questions > about it. > > 1) can I muck with it so that it functions like unmount(2) by > taking the "FSID:val0:val1" parameter in order to properly > route requests? > > 2) what if i want to pass binary data? I can do that right? > I assume by just passing the binary gook via the value of the > key value pair. > > Any comments? > > On of the issues I have is that I need the call to be callable > from both inside and outside of the kernel, I'm guessing this can > be taken care of by the internal options... > > Ideas people? > > Use nmount or sysctl? > Can't comment on your main questions, but there has been talk about removing nmount since the work was never finished and the benefits never realized. If you'd like to breath some life into it, feel free. Scott From owner-freebsd-fs@FreeBSD.ORG Sat Jul 3 19:53:47 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FE7416A4CF; Sat, 3 Jul 2004 19:53:47 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6981A43D55; Sat, 3 Jul 2004 19:53:47 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 2E25C5C86B; Sat, 3 Jul 2004 12:53:47 -0700 (PDT) Date: Sat, 3 Jul 2004 12:53:47 -0700 From: Alfred Perlstein To: Scott Long Message-ID: <20040703195347.GF95729@elvis.mu.org> References: <20040702184020.GC95729@elvis.mu.org> <40E70D90.4090304@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40E70D90.4090304@freebsd.org> User-Agent: Mutt/1.4.2.1i cc: fs@freebsd.org Subject: Re: tweaking mounted filesystems by fsid X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 19:53:47 -0000 * Scott Long [040703 12:50] wrote: > Alfred Perlstein wrote: > > > >Use nmount or sysctl? > > > > Can't comment on your main questions, but there has been talk about > removing nmount since the work was never finished and the benefits > never realized. If you'd like to breath some life into it, feel free. I'll look at it, nmount is cool, it shouldn't die. I may just use sysctl because it's what I have experience with... we'll see. -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684 From owner-freebsd-fs@FreeBSD.ORG Sat Jul 3 20:05:58 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D6DC16A4CE; Sat, 3 Jul 2004 20:05:58 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F69C43D31; Sat, 3 Jul 2004 20:05:57 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i63K5tom054740; Sat, 3 Jul 2004 22:05:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Scott Long From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 03 Jul 2004 13:48:32 MDT." <40E70D90.4090304@freebsd.org> Date: Sat, 03 Jul 2004 22:05:55 +0200 Message-ID: <54739.1088885155@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: Alfred Perlstein cc: fs@freebsd.org Subject: Re: tweaking mounted filesystems by fsid X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 20:05:58 -0000 In message <40E70D90.4090304@freebsd.org>, Scott Long writes: >Can't comment on your main questions, but there has been talk about removing nmount since the work was never finished and the benefits >never realized. If you'd like to breath some life into it, feel free. That would only give us problems. As far as I recall removing nmount would make us instantly run out of binary mount flags (the main problem which nmount was written to address). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-fs@FreeBSD.ORG Sat Jul 3 23:01:27 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5E1416A4CE; Sat, 3 Jul 2004 23:01:27 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72BB143D3F; Sat, 3 Jul 2004 23:01:27 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 5F63B5C82E; Sat, 3 Jul 2004 16:01:27 -0700 (PDT) Date: Sat, 3 Jul 2004 16:01:27 -0700 From: Alfred Perlstein To: "Tim J. Robbins" Message-ID: <20040703230127.GG95729@elvis.mu.org> References: <200407031322.i63DMdqC084182@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407031322.i63DMdqC084182@repoman.freebsd.org> User-Agent: Mutt/1.4.2.1i cc: fs@freebsd.org Subject: Re: cvs commit: src/sys/conf NOTES files options src/sys/fs/msdosfs msdosfs_fileno.c msdosfs_vfsops.c msdosfs_vnops.c msdosfsmount.h src/sys/modules/msdosfs Makefile X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 23:01:27 -0000 What are the implications of expanding the VFS API to take 64bit inodes? * Tim J. Robbins [040703 06:22] wrote: > tjr 2004-07-03 13:22:39 UTC > > FreeBSD src repository > > Modified files: > sys/conf NOTES files options > sys/fs/msdosfs msdosfs_vfsops.c msdosfs_vnops.c > msdosfsmount.h > sys/modules/msdosfs Makefile > Added files: > sys/fs/msdosfs msdosfs_fileno.c > Log: > By popular request, add a workaround that allows large (>128GB or so) > FAT32 filesystems to be mounted, subject to some fairly serious limitations. > > This works by extending the internal pseudo-inode-numbers generated from > the file's starting cluster number to 64-bits, then creating a table > mapping these into arbitrary 32-bit inode numbers, which can fit in > struct dirent's d_fileno and struct vattr's va_fileid fields. The mappings > do not persist across unmounts or reboots, so it's not possible to export > these filesystems through NFS. The mapping table may grow to be rather > large, and may grow large enough to exhaust kernel memory on filesystems > with millions of files. > > Don't enable this option unless you understand the consequences. > > Revision Changes Path > 1.1241 +12 -0 src/sys/conf/NOTES > 1.923 +1 -0 src/sys/conf/files > 1.460 +3 -0 src/sys/conf/options > 1.1 +163 -0 src/sys/fs/msdosfs/msdosfs_fileno.c (new) > 1.121 +14 -0 src/sys/fs/msdosfs/msdosfs_vfsops.c > 1.148 +33 -13 src/sys/fs/msdosfs/msdosfs_vnops.c > 1.33 +23 -1 src/sys/fs/msdosfs/msdosfsmount.h > 1.21 +4 -1 src/sys/modules/msdosfs/Makefile -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684