From owner-freebsd-fs@FreeBSD.ORG Sun Feb 15 07:30: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 9E2BD16A504; Sun, 15 Feb 2004 07:30:47 -0800 (PST) Received: from fons-adae.s.notwork.org (fons-adae.s.notwork.org [218.224.220.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 372BE43D5F; Sun, 15 Feb 2004 07:30:47 -0800 (PST) (envelope-from mrt@notwork.org) Received: from fons-adae.s.notwork.org (fons-adae.s.notwork.org [IPv6:2001:218:420::3]) by fons-adae.s.notwork.org (Postfix) with ESMTP id 313313493; Mon, 16 Feb 2004 00:30:31 +0900 (JST) To: Yar Tikhiy X-cite: xcite 1.49 From: Murata Shuuichirou In-Reply-To: <20040211183645.GA18497@comp.chem.msu.su> (Yar Tikhiy's message of "Wed, 11 Feb 2004 21:36:45 +0300") References: <87ad41z6ru.fsf@fons-adae.s.notwork.org> <20040211183645.GA18497@comp.chem.msu.su> Date: Mon, 16 Feb 2004 00:30:30 +0900 Message-ID: <87eksw1ht5.fsf@fons-adae.s.notwork.org> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/22.0.0 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: Zack Hobson cc: fs@freebsd.org Subject: Re: updating HFS for 5.2R [patch] 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: Sun, 15 Feb 2004 15:30:47 -0000 In message <20040211183645.GA18497@comp.chem.msu.su>, `yar@freebsd.org' wrote: > > But, I have not tested this fully and found some problems such as: > > > > 1. Sometime, hfs partitions become unmountable by FreeBSD > > (mount_hfs returns "Invalid argument"), although the > > partition can still be mounted by MacOSX. > > Did you try to fsck_hfs such a broken volume? Ugh, I completely forgot to do fsck. OK, fsck_hfs makes that partition mountable again. (I don't know why MacOSX was able to mount that without fsck) > > 2. After editing files on hfs filesystem with vi(1), umounting > > the filesystem causes these errors: > > > > Feb 2 21:13:11 roma kernel: hfs_fsync: dirty: 0xc2d74000: tag hfs, type VREG, usecount 2, writecount 0, refcount 2, flags (VV_SYSTEM), lock type cnode: EXCL (count 1) by thread 0xc2b42a80 (pid 1068) > > Feb 2 21:13:11 roma kernel: tag VT_HFS, cnid 4, on dev 4, 24 lock type cnode: EXCL (count 1) by thread 0xc2b42a80 (pid 1068) > > (lots of same errors continue) > > > > Then system crashed. > > It's me who introduced this bug. I forgot to unlock > a buffer at one place. Please try the patch attached. Your patch fixes the vi problem here. So HFS+ is now almost usable. -- MURATA Shuuichirou From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 04:18:37 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 4B9DC16A4CE for ; Mon, 16 Feb 2004 04:18:37 -0800 (PST) Received: from gremlin.foo.is (gremlin.foo.is [194.105.250.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2109743D1D for ; Mon, 16 Feb 2004 04:18:37 -0800 (PST) (envelope-from baldur@foo.is) Received: from 127.0.0.1 (unknown [127.0.0.1]) by injector.foo.is (Postfix) with SMTP id 8FEA53A1B9 for ; Mon, 16 Feb 2004 12:18:35 +0000 (GMT) Received: by gremlin.foo.is (Postfix, from userid 1000) id 82C913A1B8; Mon, 16 Feb 2004 12:18:30 +0000 (GMT) Date: Mon, 16 Feb 2004 12:18:30 +0000 From: Baldur Gislason To: freebsd-fs@freebsd.org Message-ID: <20040216121830.GC84940@gremlin.foo.is> User-Agent: Mutt/1.4.1i X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on gremlin.foo.is X-Spam-Level: X-Spam-Status: No, hits=-4.7 required=6.0 tests=AWL,BAYES_00 autolearn=ham version=2.61 X-Sanitizer: Foo MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Subject: Vinum and resizing filesystems 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: Mon, 16 Feb 2004 12:18:37 -0000 Is it possible to make a Vinum volume larger, and make a working UFS system larger without losing data? Baldur From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 04:44:42 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 4FDAE16A4CE for ; Mon, 16 Feb 2004 04:44:42 -0800 (PST) Received: from mailbox.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEC7F43D1F for ; Mon, 16 Feb 2004 04:44:41 -0800 (PST) (envelope-from l.ertl@univie.ac.at) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) i1GCiYlo968584; Mon, 16 Feb 2004 13:44:36 +0100 Date: Mon, 16 Feb 2004 13:44:34 +0100 (CET) From: Lukas Ertl To: Baldur Gislason In-Reply-To: <20040216121830.GC84940@gremlin.foo.is> Message-ID: <20040216134403.R71950@pcle2.cc.univie.ac.at> References: <20040216121830.GC84940@gremlin.foo.is> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: imap 4243; Body=0 Fuz1=0 Fuz2=0 cc: freebsd-fs@freebsd.org Subject: Re: Vinum and resizing filesystems 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: Mon, 16 Feb 2004 12:44:42 -0000 On Mon, 16 Feb 2004, Baldur Gislason wrote: > Is it possible to make a Vinum volume larger, and make a working UFS > system larger without losing data? Yes, add a subdisk to a plex and then use growfs to resize the filesystem. regards, le -- Lukas Ertl eMail: l.ertl@univie.ac.at UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 05:32:26 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 5847016A4D0 for ; Mon, 16 Feb 2004 05:32:26 -0800 (PST) Received: from gremlin.foo.is (gremlin.foo.is [194.105.250.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 275BE43D2F for ; Mon, 16 Feb 2004 05:32:26 -0800 (PST) (envelope-from baldur@foo.is) Received: from 127.0.0.1 (unknown [127.0.0.1]) by injector.foo.is (Postfix) with SMTP id 1FA1D3A1B9 for ; Mon, 16 Feb 2004 13:32:25 +0000 (GMT) Received: by gremlin.foo.is (Postfix, from userid 1000) id 74D463A1B8; Mon, 16 Feb 2004 13:32:19 +0000 (GMT) Date: Mon, 16 Feb 2004 13:32:19 +0000 From: Baldur Gislason To: freebsd-fs@freebsd.org Message-ID: <20040216133219.GD84940@gremlin.foo.is> User-Agent: Mutt/1.4.1i X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on gremlin.foo.is X-Spam-Level: X-Spam-Status: No, hits=-4.7 required=6.0 tests=AWL,BAYES_00 autolearn=ham version=2.61 X-Sanitizer: Foo MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Subject: Vinum, concatenated volumes and dead drives 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: Mon, 16 Feb 2004 13:32:26 -0000 With concatenated vinum volumes, if one drive dies, only the data stored on that drive will be lost and the disk label can be fixed by fsck, right? Baldur From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 06:11: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 893F016A4CE for ; Mon, 16 Feb 2004 06:11:41 -0800 (PST) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E26843D1D for ; Mon, 16 Feb 2004 06:11:38 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.9p2/8.12.9) with ESMTP id i1GEBX0V034928; Mon, 16 Feb 2004 17:11:33 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.9p2/8.12.9/Submit) id i1GEBTa0034868; Mon, 16 Feb 2004 17:11:29 +0300 (MSK) (envelope-from yar) Date: Mon, 16 Feb 2004 17:11:29 +0300 From: Yar Tikhiy To: Murata Shuuichirou Message-ID: <20040216141128.GA33847@comp.chem.msu.su> References: <87ad41z6ru.fsf@fons-adae.s.notwork.org> <20040211183645.GA18497@comp.chem.msu.su> <87eksw1ht5.fsf@fons-adae.s.notwork.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87eksw1ht5.fsf@fons-adae.s.notwork.org> User-Agent: Mutt/1.5.3i cc: fs@freebsd.org Subject: Re: updating HFS for 5.2R [patch] 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: Mon, 16 Feb 2004 14:11:41 -0000 On Mon, Feb 16, 2004 at 12:30:30AM +0900, Murata Shuuichirou wrote: > > > > 1. Sometime, hfs partitions become unmountable by FreeBSD > > > (mount_hfs returns "Invalid argument"), although the > > > partition can still be mounted by MacOSX. > > > > Did you try to fsck_hfs such a broken volume? > > Ugh, I completely forgot to do fsck. OK, fsck_hfs makes that > partition mountable again. (I don't know why MacOSX was able to > mount that without fsck) Excuse me, but did fsck_hfs show any diagnostic messages while repairing the HFS partition in FreeBSD? -- Yar From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 08:52:21 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 772AF16A4CE; Mon, 16 Feb 2004 08:52:21 -0800 (PST) Received: from fons-adae.s.notwork.org (fons-adae.s.notwork.org [218.224.220.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D4A443D2D; Mon, 16 Feb 2004 08:52:21 -0800 (PST) (envelope-from mrt@notwork.org) Received: from fons-adae.s.notwork.org (fons-adae.s.notwork.org [IPv6:2001:218:420::3]) by fons-adae.s.notwork.org (Postfix) with ESMTP id 86F633482; Tue, 17 Feb 2004 01:52:18 +0900 (JST) To: Yar Tikhiy X-cite: xcite 1.49 From: Murata Shuuichirou In-Reply-To: <20040216141128.GA33847@comp.chem.msu.su> (Yar Tikhiy's message of "Mon, 16 Feb 2004 17:11:29 +0300") References: <87eksw1ht5.fsf@fons-adae.s.notwork.org> <20040216141128.GA33847@comp.chem.msu.su> Date: Tue, 17 Feb 2004 01:52:17 +0900 Message-ID: <87isi77yri.fsf@fons-adae.s.notwork.org> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/22.0.0 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: fs@freebsd.org Subject: Re: updating HFS for 5.2R [patch] 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: Mon, 16 Feb 2004 16:52:21 -0000 In message <20040216141128.GA33847@comp.chem.msu.su>, `yar@freebsd.org' wrote: > > > > 1. Sometime, hfs partitions become unmountable by FreeBSD > > > > (mount_hfs returns "Invalid argument"), although the > > > > partition can still be mounted by MacOSX. > > > > > > Did you try to fsck_hfs such a broken volume? > > > > Ugh, I completely forgot to do fsck. OK, fsck_hfs makes that > > partition mountable again. (I don't know why MacOSX was able to > > mount that without fsck) > > Excuse me, but did fsck_hfs show any diagnostic messages while > repairing the HFS partition in FreeBSD? Sorry, the problem has been occured on a machine of a friend who is testing hfs on FreeBSD. So I didn't see the problem by myself actually. She (the tester) said, "IIRC, nothing special was printed by fsck_hfs, and I cannot reproduce the problem yet." -- MURATA Shuuichirou From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 15:22:49 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 C87F616A4CE for ; Mon, 16 Feb 2004 15:22:49 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F81B43D1D for ; Mon, 16 Feb 2004 15:22:49 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id EBC562BD4D for ; Tue, 17 Feb 2004 10:22:47 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id CF62951200; Tue, 17 Feb 2004 09:52:45 +1030 (CST) Date: Tue, 17 Feb 2004 09:52:45 +1030 From: Greg 'groggy' Lehey To: Lukas Ertl Message-ID: <20040216232245.GS33797@wantadilla.lemis.com> References: <20040216121830.GC84940@gremlin.foo.is> <20040216134403.R71950@pcle2.cc.univie.ac.at> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FLH4cmKOuTk9RMdw" Content-Disposition: inline In-Reply-To: <20040216134403.R71950@pcle2.cc.univie.ac.at> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-fs@freebsd.org cc: Baldur Gislason Subject: Re: Vinum and resizing filesystems 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: Mon, 16 Feb 2004 23:22:49 -0000 --FLH4cmKOuTk9RMdw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 16 February 2004 at 13:44:34 +0100, Lukas Ertl wrote: > On Mon, 16 Feb 2004, Baldur Gislason wrote: > >> Is it possible to make a Vinum volume larger, and make a working UFS >> system larger without losing data? > > Yes, add a subdisk to a plex and then use growfs to resize the filesystem. Note that there are still some issues with UFS2 and growfs. They're being looked at. Greg -- See complete headers for address and phone numbers. --FLH4cmKOuTk9RMdw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFAMVDFIubykFB6QiMRAvk5AKCwRcq6NxP8KosgbfEg5f+C7HeSkgCgofqO GNufpBdc2AGD364E/gxpkog= =YV9+ -----END PGP SIGNATURE----- --FLH4cmKOuTk9RMdw-- From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 16:04:12 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 D56EE16A4CE; Mon, 16 Feb 2004 16:04:12 -0800 (PST) Received: from randomservers.com (randomservers.com [69.55.237.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id C501743D1D; Mon, 16 Feb 2004 16:04:12 -0800 (PST) (envelope-from joseph@randomnetworks.com) Received: from randomservers.com (randomservers [69.55.237.158]) by randomservers.com (8.12.10/8.12.6) with ESMTP id i1H02Hwn016774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Feb 2004 16:02:17 -0800 (PST) (envelope-from joseph@randomnetworks.com) X-Authentication-Warning: randomservers.com: Host randomservers [69.55.237.158] claimed to be randomservers.com Received: from localhost (joseph@localhost)i1H02H7m016766; Mon, 16 Feb 2004 16:02:17 -0800 (PST) (envelope-from joseph@randomnetworks.com) X-Authentication-Warning: randomservers.com: joseph owned process doing -bs Date: Mon, 16 Feb 2004 16:02:17 -0800 (PST) From: Joseph Scott X-X-Sender: joseph@randomservers To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, mckusick@freebsd.org, scottl@freebsd.org Message-ID: <20040216155005.J4957@randomservers> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=0.0 required=7.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on randomservers.com Subject: FreeBSD 5.2.1-RC2 fs snapshot problems. 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: Tue, 17 Feb 2004 00:04:13 -0000 I just finished testing a fresh install of FreeBSD 5.2.1-RC2 and have verified that the problem mentioned in PR kern/58154 is still there. The problem is fairly simple to show: 1. Install a fresh 5.2.1-RC2 system. 2. Shutdown a few times to show that it completes correctly. 3. Create some snapshots of a filesystem (on 5.2.1-RC2 I did 3 snapshots of /usr). 4. Try to shutdown again. 5. Watch your system hang forever, unable to complete a shutdown correctly. I've done this samething on 3 different systems with the exact same results every single time. If you cycle the power to reboot and then delete the snapshot files shutdown is able to work completely once more. I'm more than willing to try out patches or different settings/options in an effort to try and track this down. I would be thrilled to be able to use fs snapshots for systems at work, but as it stands not being able to shutdown a system makes the snapshot feature useless. Sorry about cross posting this so much, but I've been trying to raise the attention level of this problem for weeks now without any luck. -- Joseph Scott http://www.randomnetworks.com/joseph/blog/contact.php From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 17:01:57 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 8072016A4CE; Mon, 16 Feb 2004 17:01:57 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53A8D43D1D; Mon, 16 Feb 2004 17:01:57 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i1H11k7E048190; Mon, 16 Feb 2004 17:01:50 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200402170101.i1H11k7E048190@gw.catspoiler.org> Date: Mon, 16 Feb 2004 17:01:46 -0800 (PST) From: Don Lewis To: joseph@randomnetworks.com In-Reply-To: <20040216155005.J4957@randomservers> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-fs@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: scottl@FreeBSD.org cc: mckusick@FreeBSD.org Subject: Re: FreeBSD 5.2.1-RC2 fs snapshot problems. 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: Tue, 17 Feb 2004 01:01:57 -0000 On 16 Feb, Joseph Scott wrote: > > I just finished testing a fresh install of FreeBSD 5.2.1-RC2 and > have verified that the problem mentioned in PR kern/58154 is still there. > The problem is fairly simple to show: > > 1. Install a fresh 5.2.1-RC2 system. > 2. Shutdown a few times to show that it completes correctly. > 3. Create some snapshots of a filesystem (on 5.2.1-RC2 I did > 3 snapshots of /usr). > 4. Try to shutdown again. > 5. Watch your system hang forever, unable to complete a shutdown > correctly. > > I've done this samething on 3 different systems with the exact > same results every single time. If you cycle the power to reboot and then > delete the snapshot files shutdown is able to work completely once more. > > I'm more than willing to try out patches or different > settings/options in an effort to try and track this down. I would be > thrilled to be able to use fs snapshots for systems at work, but as it > stands not being able to shutdown a system makes the snapshot feature > useless. > > Sorry about cross posting this so much, but I've been trying to > raise the attention level of this problem for weeks now without any luck. I saw this as well a couple of months ago. I think I was running 5.2-CURRENT. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 18:00: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 1574C16A4CE for ; Mon, 16 Feb 2004 18:00:39 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFE3243D31 for ; Mon, 16 Feb 2004 18:00:38 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id 944F02BD4A for ; Tue, 17 Feb 2004 13:00:36 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 52BB151204; Tue, 17 Feb 2004 12:30:34 +1030 (CST) Date: Tue, 17 Feb 2004 12:30:34 +1030 From: Greg 'groggy' Lehey To: Baldur Gislason Message-ID: <20040217020034.GZ33797@wantadilla.lemis.com> References: <20040216133219.GD84940@gremlin.foo.is> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NJGH6qcD7M1vSGDg" Content-Disposition: inline In-Reply-To: <20040216133219.GD84940@gremlin.foo.is> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-fs@freebsd.org Subject: Re: Vinum, concatenated volumes and dead drives 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: Tue, 17 Feb 2004 02:00:39 -0000 --NJGH6qcD7M1vSGDg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 16 February 2004 at 13:32:19 +0000, Baldur Gislason wrote: > With concatenated vinum volumes, if one drive dies, only the data > stored on that drive will be lost and the disk label can be fixed by > fsck, right? Well, firstly there's no such thing as a concatenated volume: it's a concatenated plex. If you have a volume with only a concatenated plex, and you lose a drive, then yes, you only lose the data on that drive. I've never tried it, but I suspect that fsck would have a hard time recreating the file system if any sizeable chunk is missing. In general, I'd expect that you lose your file system under these circumstances. Greg -- See complete headers for address and phone numbers. --NJGH6qcD7M1vSGDg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFAMXXCIubykFB6QiMRAukMAJ9G7vfrgroQPv0q8U99/vkbXHISFgCgjgt6 e7k/StR7n+q2QN94dgrQb0M= =R9PF -----END PGP SIGNATURE----- --NJGH6qcD7M1vSGDg-- From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 20:20:11 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 012B016A4CF; Mon, 16 Feb 2004 20:20:11 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA55343D2D; Mon, 16 Feb 2004 20:20:10 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i1H4JeDL085259; Mon, 16 Feb 2004 23:19:40 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i1H4JeSA085256; Mon, 16 Feb 2004 23:19:40 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 16 Feb 2004 23:19:40 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Greg 'groggy' Lehey" In-Reply-To: <20040217020034.GZ33797@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-fs@FreeBSD.org cc: Baldur Gislason Subject: Re: Vinum, concatenated volumes and dead drives 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: Tue, 17 Feb 2004 04:20:11 -0000 On Tue, 17 Feb 2004, Greg 'groggy' Lehey wrote: > I've never tried it, but I suspect that fsck would have a hard time > recreating the file system if any sizeable chunk is missing. In > general, I'd expect that you lose your file system under these > circumstances. I've run into a number of situations where fsck is unable to recover from catastrophic loss, such as wholesale stamping of zero's over the alternative superblock and meta-data. Under those circumstances, newfs is a lot easier to use than fsck. Our kernel implementation makes fairly strong assumptions about the correctness of on-disk contents, and is not resilient to some of the nastier failure modes associated with zeroing (losing) large chunks of meta-data, and I've also found fsdb doesn't like them much either (especially when you have a broken first alternate superblock). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research From owner-freebsd-fs@FreeBSD.ORG Tue Feb 17 15:05:17 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 CC01F16A4CE for ; Tue, 17 Feb 2004 15:05:17 -0800 (PST) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1489843D31 for ; Tue, 17 Feb 2004 15:05:17 -0800 (PST) (envelope-from rainer@ultra-secure.de) Received: (qmail 23437 invoked by uid 85); 17 Feb 2004 23:05:15 -0000 Received: from rainer@ultra-secure.de by bsd.ultra-secure.de by uid 89 with qmail-scanner-1.16 (clamscan: 0.65. spamassassin: 2.60. Clear:. Processed in 0.437064 secs); 17 Feb 2004 23:05:15 -0000 Received: from unknown (HELO ultra-secure.de) (rainer@ultra-secure.de@217.232.216.113) by bsd.ultra-secure.de with AES256-SHA encrypted SMTP; 17 Feb 2004 23:05:14 -0000 Message-ID: <40329E22.6000501@ultra-secure.de> Date: Wed, 18 Feb 2004 00:05:06 +0100 From: Rainer Duffner User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030821 X-Accept-Language: en-us, en MIME-Version: 1.0 To: fs@freebsd.org X-Enigmail-Version: 0.76.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Is it possible to re-create the disklabel ? 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: Tue, 17 Feb 2004 23:05:17 -0000 Hi, somehow, my disklabel seems to have gotten ruined. (with grub): "invalid label" "invalid label" "No boot/loader" I suspect knoppix... The partition is still seen as "BSD", but with sysinstall, I can't see the slices anymore. How can I recreate the disklabel ? Thanks in advance, Rainer From owner-freebsd-fs@FreeBSD.ORG Tue Feb 17 17:17:05 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 1C7E316A4D1 for ; Tue, 17 Feb 2004 17:17:05 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id D0A6C43D1D for ; Tue, 17 Feb 2004 17:17:04 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 88098 invoked by uid 1002); 18 Feb 2004 01:17:02 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 18 Feb 2004 01:17:02 -0000 Message-ID: <4032BC6A.7030403@freebsd.org> Date: Tue, 17 Feb 2004 18:14:18 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Lewis References: <200402170101.i1H11k7E048190@gw.catspoiler.org> In-Reply-To: <200402170101.i1H11k7E048190@gw.catspoiler.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-fs@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: joseph@randomnetworks.com cc: mckusick@FreeBSD.org Subject: Re: FreeBSD 5.2.1-RC2 fs snapshot problems. 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: Wed, 18 Feb 2004 01:17:05 -0000 Don Lewis wrote: > On 16 Feb, Joseph Scott wrote: > >> I just finished testing a fresh install of FreeBSD 5.2.1-RC2 and >>have verified that the problem mentioned in PR kern/58154 is still there. >>The problem is fairly simple to show: >> >>1. Install a fresh 5.2.1-RC2 system. >>2. Shutdown a few times to show that it completes correctly. >>3. Create some snapshots of a filesystem (on 5.2.1-RC2 I did >> 3 snapshots of /usr). >>4. Try to shutdown again. >>5. Watch your system hang forever, unable to complete a shutdown >> correctly. >> >> I've done this samething on 3 different systems with the exact >>same results every single time. If you cycle the power to reboot and then >>delete the snapshot files shutdown is able to work completely once more. >> >> I'm more than willing to try out patches or different >>settings/options in an effort to try and track this down. I would be >>thrilled to be able to use fs snapshots for systems at work, but as it >>stands not being able to shutdown a system makes the snapshot feature >>useless. >> >> Sorry about cross posting this so much, but I've been trying to >>raise the attention level of this problem for weeks now without any luck. > > > I saw this as well a couple of months ago. I think I was running > 5.2-CURRENT. > There are fundamental issues with FFS snapshots and our buffer/cache that are well beyond the scope of fixing for 5.2.1. If someone has an idea of how to fix them for 5.3, all the better. Scott From owner-freebsd-fs@FreeBSD.ORG Wed Feb 18 02:11:18 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 18B7416A4CF for ; Wed, 18 Feb 2004 02:11:18 -0800 (PST) Received: from gremlin.foo.is (gremlin.foo.is [194.105.250.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9F3243D1D for ; Wed, 18 Feb 2004 02:11:17 -0800 (PST) (envelope-from baldur@foo.is) Received: from 127.0.0.1 (unknown [127.0.0.1]) by injector.foo.is (Postfix) with SMTP id CA14F3A2FF for ; Wed, 18 Feb 2004 10:11:15 +0000 (GMT) Received: by gremlin.foo.is (Postfix, from userid 1000) id 526AB3A2FE; Wed, 18 Feb 2004 10:11:10 +0000 (GMT) Date: Wed, 18 Feb 2004 10:11:10 +0000 From: Baldur Gislason To: freebsd-fs@freebsd.org Message-ID: <20040218101110.GB6490@gremlin.foo.is> User-Agent: Mutt/1.4.1i X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on gremlin.foo.is X-Spam-Level: X-Spam-Status: No, hits=-4.7 required=6.0 tests=AWL,BAYES_00 autolearn=ham version=2.61 X-Sanitizer: Foo MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Subject: Filesystems bigger than 1TB.... possible? 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: Wed, 18 Feb 2004 10:11:18 -0000 I've ran into problems using growfs to grow filesystems above 1TB, is it possible at all to have filesystems this big or am I forced to split things up? Baldur From owner-freebsd-fs@FreeBSD.ORG Wed Feb 18 09:58:57 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 0139816A4CE for ; Wed, 18 Feb 2004 09:58:57 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id E26DA43D1D for ; Wed, 18 Feb 2004 09:58:56 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i1IHwo2h020392; Wed, 18 Feb 2004 09:58:50 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i1IHwom0020391; Wed, 18 Feb 2004 09:58:50 -0800 Date: Wed, 18 Feb 2004 09:58:50 -0800 From: Brooks Davis To: Baldur Gislason Message-ID: <20040218175850.GA30941@Odin.AC.HMC.Edu> References: <20040218101110.GB6490@gremlin.foo.is> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <20040218101110.GB6490@gremlin.foo.is> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-fs@freebsd.org Subject: Re: Filesystems bigger than 1TB.... possible? 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: Wed, 18 Feb 2004 17:58:57 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 18, 2004 at 10:11:10AM +0000, Baldur Gislason wrote: > I've ran into problems using growfs to grow filesystems above 1TB, > is it possible at all to have filesystems this big or am I forced to > split things up? [9:56am] brooks@nmirror (/usr/mirror/scripts): uname -m -r -s FreeBSD 5.2-CURRENT i386 [9:56am] brooks@nmirror (/usr/mirror/scripts): df -h /mirrors Filesystem Size Used Avail Capacity Mounted on /dev/twed0s2 1.8T 935G 772G 55% /mirrors sysinstall can't create MBR partitions larger then around 1TB, but you can install the OS on a small partition leaving the reset unallocated and then use the fdisk utility to create a large partition. In practice, you need 5.x to make this work. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAM6fZXY6L6fI4GtQRAvZ7AJ9J/RRYLmY/3+5D6oro/6ar9ws0yACfcl3b KicyeOtn+BIPV+oBY+NspsQ= =+5rp -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 18 14:29:48 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 CAB4F16A4CE; Wed, 18 Feb 2004 14:29:48 -0800 (PST) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88DB343D1F; Wed, 18 Feb 2004 14:29:48 -0800 (PST) (envelope-from mi+mx@aldan.algebra.com) Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])i1IMTIlP054236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 18 Feb 2004 17:29:47 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (mteterin@localhost [127.0.0.1]) i1IMT6w3072596; Wed, 18 Feb 2004 17:29:07 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) From: mi+mx@aldan.algebra.com Organization: Murex N.A. To: fs@FreeBSD.org, performance@FreeBSD.org Date: Wed, 18 Feb 2004 17:29:06 -0500 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402181729.06202@misha-mx.virtual-estates.net> X-Scanned-By: MIMEDefang 2.39 Subject: strange performance dip shown by iozone 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: Wed, 18 Feb 2004 22:29:48 -0000 Hello! I'm trying to tune the amrd-based RAID5 and have made several iozone runs on the array and -- for comparision -- on the single disk connected to the Serial ATA controller directly. The RAID-based FS was newfs-ed with ``-b 65536'', as it is intended to store very large files. The single-disk FS was newfs-ed with defaults. No softupdates were enabled on either, since those seem to degrade iozone results slightly (iozone reads/writes a single file anyway). The filesystems displayed different performance (reads are better with RAID, writes -- with the single disk), but both have shown a notable dip in writing (and re-writing) speed when iozone used the record lengthes of 128 and 256. Can someone explain that? Is that a known fact? How can that be avoided? The machine is an amd64 running a fresh -current. The disks are 200Gb SATAs. RAID5 consists of 6 of them. Thanks! -mi From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 05:33:36 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 3FBA016A4CE; Thu, 19 Feb 2004 05:33:36 -0800 (PST) Received: from relay.kiev.sovam.com (relay.kiev.sovam.com [212.109.32.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C562343D1F; Thu, 19 Feb 2004 05:33:35 -0800 (PST) (envelope-from dimitry@al.org.ua) Received: from [212.109.32.116] (helo=svitonline.com) by relay.kiev.sovam.com with esmtp (Exim 4.30) id 1AtoJ4-000HPn-1E; Thu, 19 Feb 2004 15:33:34 +0200 From: Dmitry Alyabyev To: freebsd-fs@freebsd.org Date: Thu, 19 Feb 2004 15:33:33 +0200 User-Agent: KMail/1.6 References: <200402181729.06202@misha-mx.virtual-estates.net> In-Reply-To: <200402181729.06202@misha-mx.virtual-estates.net> X-NCC-RegID: ua.svitonline MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200402191533.33495.dimitry@al.org.ua> X-Scanner-Signature: e35cef5ed21d82303c208435479e4a86 X-DrWeb-checked: yes cc: performance@FreeBSD.org Subject: Re: strange performance dip shown by iozone X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dimitry@al.org.ua List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 13:33:36 -0000 On Thursday 19 February 2004 00:29, mi+mx@aldan.algebra.com wrote: > Hello! > > I'm trying to tune the amrd-based RAID5 and have made several iozone > runs on the array and -- for comparision -- on the single disk connected > to the Serial ATA controller directly. > > The RAID-based FS was newfs-ed with ``-b 65536'', as it is intended to > store very large files. The single-disk FS was newfs-ed with defaults. > > No softupdates were enabled on either, since those seem to degrade iozone > results slightly (iozone reads/writes a single file anyway). > > The filesystems displayed different performance (reads are better with > RAID, writes -- with the single disk), but both have shown a notable dip > in writing (and re-writing) speed when iozone used the record lengthes > of 128 and 256. Can someone explain that? Is that a known fact? How can > that be avoided? > > The machine is an amd64 running a fresh -current. The disks are 200Gb > SATAs. RAID5 consists of 6 of them. which stripe size of RAID5 did you use ? -- Dimitry From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 23:23: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 D4DAE16A4CE; Thu, 19 Feb 2004 23:23:39 -0800 (PST) Received: from VARK.homeunix.com (adsl-68-122-0-124.dsl.pltn13.pacbell.net [68.122.0.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id B245F43D1D; Thu, 19 Feb 2004 23:23:39 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.11/8.12.10) with ESMTP id i1K7Mwkl017628; Thu, 19 Feb 2004 23:22:58 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i1K7MwM4017627; Thu, 19 Feb 2004 23:22:58 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Thu, 19 Feb 2004 23:22:58 -0800 From: David Schultz To: mi+mx@aldan.algebra.com Message-ID: <20040220072258.GA17579@VARK.homeunix.com> Mail-Followup-To: mi+mx@aldan.algebra.com, fs@FreeBSD.ORG, performance@FreeBSD.ORG References: <200402181729.06202@misha-mx.virtual-estates.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402181729.06202@misha-mx.virtual-estates.net> cc: performance@FreeBSD.ORG cc: fs@FreeBSD.ORG Subject: Re: strange performance dip shown by iozone 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, 20 Feb 2004 07:23:40 -0000 On Wed, Feb 18, 2004, mi+mx@aldan.algebra.com wrote: > I'm trying to tune the amrd-based RAID5 and have made several iozone > runs on the array and -- for comparision -- on the single disk connected > to the Serial ATA controller directly. [...] > The filesystems displayed different performance (reads are better with > RAID, writes -- with the single disk), but both have shown a notable dip > in writing (and re-writing) speed when iozone used the record lengthes > of 128 and 256. Can someone explain that? Is that a known fact? How can > that be avoided? This is known as the small write problem for RAID 5. Basically, any write smaller than the RAID 5 stripe size is performed using an expensive read-modify-write operation so that the parity can be recomputed. The solution is to not do that. If you expect lots of small random writes and you can't do anything about it, you need to either use RAID 1 instead of RAID 5, or use a log-structured filesystem, such as NetBSD's LFS. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 04:11: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 43ED416A4CE; Fri, 20 Feb 2004 04:11:39 -0800 (PST) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id D05E743D2D; Fri, 20 Feb 2004 04:11:38 -0800 (PST) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.10/8.12.10/NinthNine) with ESMTP id i1KCBbXh087403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2004 21:11:37 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Fri, 20 Feb 2004 21:11:37 +0900 (JST) Message-Id: <200402201211.i1KCBbXh087403@sakura.ninth-nine.com> From: Norikatsu Shigemura To: fs@FreeBSD.org X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: yar@FreeBSD.org Subject: Cannot build hfs-freebsd-03p1 on 5-current 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, 20 Feb 2004 12:11:39 -0000 Hum.. I can't compile hfs-freebsd-03p1 on 5-current. Anyone, do you know this fix? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ cd /tmp $ tar xvfz hfs-freebsd-03p1.tar.gz $ cd hfs-freebsd-03p1 $ make : : cc -O -fno-ident -pipe -march=pentium3 -I/tmp/hfs-freebsd-03p1/freebsd/hfs/../../darwin/xnu/bsd -I/tmp/hfs-freebsd-03p1/freebsd/hfs/../../darwin/xnu/bsd/hfs -I/tmp/hfs-freebsd-03p1/freebsd/hfs/../../darwin/xnu/bsd/hfs/hfscommon/headers -D_KERNEL -DKLD_MODULE -nostdinc -I- -I/tmp/hfs-freebsd-03p1/freebsd/hfs/../../darwin/xnu/bsd -I/tmp/hfs-freebsd-03p1/freebsd/hfs/../../darwin/xnu/bsd/hfs -I/tmp/hfs-freebsd-03p1/freebsd/hfs/../../darwin/xnu/bsd/hfs/hfscommon/headers -I. -I@ -I@/../include -I/usr/include -finline-limit=15000 -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -c /tmp/hfs-freebsd-03p1/freebsd/hfs/../../darwin/xnu/bsd/hfs/hfs_readwrite.c /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c: In function `hfs_write': /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c:341: error: structure has no member named `p_rlimit' /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c: In function `hfs_bmap': /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c:976: warning: enumeration value `RL_NOOVERLAP' not handled in switch *** Error code 1 Stop in /tmp/hfs-freebsd-03p1/freebsd/hfs. *** Error code 1 Stop in /tmp/hfs-freebsd-03p1/freebsd. *** Error code 1 Stop in /tmp/hfs-freebsd-03p1. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 05:41:02 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 987E216A4CE; Fri, 20 Feb 2004 05:41:02 -0800 (PST) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 179AB43D2D; Fri, 20 Feb 2004 05:41:01 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.9p2/8.12.9) with ESMTP id i1KDeu0V094140; Fri, 20 Feb 2004 16:40:56 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.9p2/8.12.9/Submit) id i1KDetQ7094105; Fri, 20 Feb 2004 16:40:55 +0300 (MSK) (envelope-from yar) Date: Fri, 20 Feb 2004 16:40:54 +0300 From: Yar Tikhiy To: Norikatsu Shigemura Message-ID: <20040220134054.GD91603@comp.chem.msu.su> References: <200402201211.i1KCBbXh087403@sakura.ninth-nine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402201211.i1KCBbXh087403@sakura.ninth-nine.com> User-Agent: Mutt/1.5.3i cc: fs@FreeBSD.org Subject: Re: Cannot build hfs-freebsd-03p1 on 5-current 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, 20 Feb 2004 13:41:02 -0000 On Fri, Feb 20, 2004 at 09:11:37PM +0900, Norikatsu Shigemura wrote: > Hum.. I can't compile hfs-freebsd-03p1 on 5-current. > Anyone, do you know this fix? [...] > /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c: In function `hfs_write': > /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c:341: error: structure has no member named `p_rlimit' I believe that was due to a recent change in the per-process rlimit structure. Would you mind trying the patch attached below? -- Yar --- hfs_readwrite.c 7 Feb 2004 17:27:43 -0000 1.40.2.2 +++ hfs_readwrite.c 20 Feb 2004 13:07:14 -0000 @@ -337,12 +337,14 @@ hfs_write(ap) * file servers have no limits, I don't think it matters. */ p = uio->uio_td; - if (vp->v_type == VREG && p && - writelimit > p->td_proc->p_rlimit[RLIMIT_FSIZE].rlim_cur) { + if (vp->v_type == VREG && p != NULL) { PROC_LOCK(p->td_proc); - psignal(p->td_proc, SIGXFSZ); + if (writelimit > lim_cur(p->td_proc, RLIMIT_FSIZE)) { + psignal(p->td_proc, SIGXFSZ); + PROC_UNLOCK(p->td_proc); + return (EFBIG); + } PROC_UNLOCK(p->td_proc); - return (EFBIG); } p = current_proc(); From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 05:50:48 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 DE78116A4CE; Fri, 20 Feb 2004 05:50:48 -0800 (PST) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 680E743D1D; Fri, 20 Feb 2004 05:50:48 -0800 (PST) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.10/8.12.10/NinthNine) with ESMTP id i1KDokXh089778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2004 22:50:47 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Fri, 20 Feb 2004 22:50:47 +0900 (JST) Message-Id: <200402201350.i1KDokXh089778@sakura.ninth-nine.com> From: Norikatsu Shigemura To: Yar Tikhiy In-Reply-To: <20040220134054.GD91603@comp.chem.msu.su> References: <200402201211.i1KCBbXh087403@sakura.ninth-nine.com> <20040220134054.GD91603@comp.chem.msu.su> X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: fs@FreeBSD.org Subject: Re: Cannot build hfs-freebsd-03p1 on 5-current 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, 20 Feb 2004 13:50:49 -0000 Hi Yar! On Fri, 20 Feb 2004 16:40:54 +0300 Yar Tikhiy wrote: > On Fri, Feb 20, 2004 at 09:11:37PM +0900, Norikatsu Shigemura wrote: > > Hum.. I can't compile hfs-freebsd-03p1 on 5-current. > > Anyone, do you know this fix? > [...] > > /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c: In function `hfs_write': > > /tmp/hfs-freebsd-03p1/darwin/xnu/bsd/hfs/hfs_readwrite.c:341: error: structure has no member named `p_rlimit' > I believe that was due to a recent change in the per-process rlimit structure. > Would you mind trying the patch attached below? Thank you for your patch. I could compile it, and I'll try to run! From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 07:09: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 1862A16A4CE; Fri, 20 Feb 2004 07:09:41 -0800 (PST) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E38C43D2D; Fri, 20 Feb 2004 07:09:40 -0800 (PST) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.10/8.12.10/NinthNine) with ESMTP id i1KF9aXh069869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2004 00:09:37 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sat, 21 Feb 2004 00:09:37 +0900 (JST) Message-Id: <200402201509.i1KF9aXh069869@sakura.ninth-nine.com> From: Norikatsu Shigemura To: Yar Tikhiy In-Reply-To: <200402201350.i1KDokXh089778@sakura.ninth-nine.com> References: <200402201211.i1KCBbXh087403@sakura.ninth-nine.com> <20040220134054.GD91603@comp.chem.msu.su> <200402201350.i1KDokXh089778@sakura.ninth-nine.com> X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: fs@FreeBSD.org Subject: Re: Cannot build hfs-freebsd-03p1 on 5-current 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, 20 Feb 2004 15:09:41 -0000 On Fri, 20 Feb 2004 22:50:47 +0900 (JST) Norikatsu Shigemura wrote: > Thank you for your patch. I could compile it, and I'll > try to run! Cool! It's a great. I confirm to newfs_hfs/mount_hfs/fsck_hfs with /dev/md0. Hummm..... I wanted to get iPod! :-) # Hi ume@, I'm ready to get your iPod! From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 07:51:03 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 1703816A4CE; Fri, 20 Feb 2004 07:51:03 -0800 (PST) Received: from cheer.mahoroba.org (flets20-024.kamome.or.jp [218.45.20.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CB9D43D2F; Fri, 20 Feb 2004 07:51:02 -0800 (PST) (envelope-from ume@FreeBSD.org) Received: from lyrics.mahoroba.org (IDENT:oLzkyISK/7gpFxTFnvZ2UciBaq4zWphg@lyrics.mahoroba.org [192.168.100.47]) (user=ume mech=CRAM-MD5 bits=0)i1KFonZS052165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2004 00:50:56 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Sat, 21 Feb 2004 00:50:48 +0900 Message-ID: From: Hajimu UMEMOTO To: Norikatsu Shigemura In-Reply-To: <200402201509.i1KF9aXh069869@sakura.ninth-nine.com> References: <200402201211.i1KCBbXh087403@sakura.ninth-nine.com> <20040220134054.GD91603@comp.chem.msu.su> <200402201350.i1KDokXh089778@sakura.ninth-nine.com> <200402201509.i1KF9aXh069869@sakura.ninth-nine.com> User-Agent: xcite1.38> Wanderlust/2.11.3 (Wonderwall) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 5.2-CURRENT MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on cheer.mahoroba.org cc: Yar Tikhiy cc: fs@FreeBSD.org Subject: Re: Cannot build hfs-freebsd-03p1 on 5-current 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, 20 Feb 2004 15:51:03 -0000 Hi, >>>>> On Sat, 21 Feb 2004 00:09:37 +0900 (JST) >>>>> Norikatsu Shigemura said: nork> Hummm..... I wanted to get iPod! :-) I believe you'll buy iPod for your own. Fortunately, tomorroy is good holiday for shopping. :) nork> # Hi ume@, I'm ready to get your iPod! Too late. My iPod was initialized to FAT32, and I'm happy with gtkpod and Simokawa-san's firefire stuff on FreeBSD, already.:-) Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 08:47: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 6EAB116A4CE; Fri, 20 Feb 2004 08:47:58 -0800 (PST) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 125D543D2F; Fri, 20 Feb 2004 08:47:58 -0800 (PST) (envelope-from mi+mx@aldan.algebra.com) Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])i1KGlN3R085326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 20 Feb 2004 11:47:56 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (mteterin@localhost [127.0.0.1]) i1KGl4w3084778; Fri, 20 Feb 2004 11:47:05 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) From: mi+mx@aldan.algebra.com Organization: Murex N.A. To: David Schultz Date: Fri, 20 Feb 2004 11:47:03 -0500 User-Agent: KMail/1.5.4 References: <200402181729.06202@misha-mx.virtual-estates.net> <20040220072258.GA17579@VARK.homeunix.com> In-Reply-To: <20040220072258.GA17579@VARK.homeunix.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402201147.03606@misha-mx.virtual-estates.net> X-Scanned-By: MIMEDefang 2.39 cc: performance@FreeBSD.ORG cc: fs@FreeBSD.ORG Subject: Re: strange performance dip shown by iozone 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, 20 Feb 2004 16:47:58 -0000 On Wed, Feb 18, 2004, mi+mx@aldan.algebra.com wrote: => I'm trying to tune the amrd-based RAID5 and have made several iozone => runs on the array and -- for comparision -- on the single disk => connected to the Serial ATA controller directly. [...] => The filesystems displayed different performance (reads are better => with RAID, writes -- with the single disk), but both have shown a => notable dip in writing (and re-writing) speed when iozone used the => record lengthes of 128 and 256. Can someone explain that? Is that a => known fact? How can that be avoided? =This is known as the small write problem for RAID 5. Basically, =any write smaller than the RAID 5 stripe size is performed using =an expensive read-modify-write operation so that the parity can be =recomputed. I don't think, this is a valid explanation. First, there is no "performance climb" as the record length goes up, there is a "dip". In case of RAID5 it starts at higher level at reclen 4, decreases slowly to 128 and then drops dramaticly at record lengths of 256 and 512, to climb back up at 1024 and stay up. Here is the iozone's output to illustrate: Size: RAID5: Single disk: KB reclen write write (Kb/second) 2097152 4 18625 17922 2097152 8 16794 17004 2097152 16 15744 23967 2097152 32 15514 20476 2097152 64 14693 18245 2097152 128 12518 17598 2097152 256 6370 29418 2097152 512 8596 35997 2097152 1024 16015 36098 2097152 2048 15588 35207 2097152 4096 16016 36832 2097152 8192 15907 37927 2097152 16384 15810 32620 I'd dismiss it as the controller's heurestics' artifact, but the single disk results show a similar (if not as profound) pattern of write performance changes. Could there be something about the FS? Also, is the RAID5 writing speed supposed to be _so much_ worse, than that of a single disk? =The solution is to not do that. If you expect lots of small random =writes and you can't do anything about it, you need to either use =RAID 1 instead of RAID 5, or use a log-structured filesystem, such as =NetBSD's LFS. This partition is intended to store huge backup files (database dumps mostly). Reading and writing will, likely, be limited by the (de)compression speed anyway, so the I/O performance is satisfactory as it is. I just wanted to have some benchmarks to help us decide, what to get for other uses in the future. Thanks! -mi From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 19:37:45 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 44BCC16A4CE for ; Fri, 20 Feb 2004 19:37:45 -0800 (PST) Received: from web13425.mail.yahoo.com (web13425.mail.yahoo.com [216.136.175.156]) by mx1.FreeBSD.org (Postfix) with SMTP id 28A3243D1F for ; Fri, 20 Feb 2004 19:37:45 -0800 (PST) (envelope-from giffunip@yahoo.com) Message-ID: <20040221033745.78201.qmail@web13425.mail.yahoo.com> Received: from [63.171.232.249] by web13425.mail.yahoo.com via HTTP; Sat, 21 Feb 2004 03:37:45 GMT Date: Sat, 21 Feb 2004 03:37:45 +0000 (GMT) From: "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" To: freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: BFS book now free ! X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: giffunip@asme.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 03:37:45 -0000 Hi; Just a short note to mention that Dominic Giampolo (BeFS creator now working on Apple) has released a copy of his book on Acrobat's .pdf format: http://www.nobius.org/~dbg/practical-file-system-design.pdf The book was also the base for a BSD licensed filesystem from some other guys: http://www.bug-br.org.br/openbfs/ enjoy and, of course, thanks to Dominic :), Pedro. ___________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html From owner-freebsd-fs@FreeBSD.ORG Sat Feb 21 13:32:37 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7D55316A4CE; Sat, 21 Feb 2004 13:32:37 -0800 (PST) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.10/8.12.9) with ESMTP id i1LLWaHS057633; Sat, 21 Feb 2004 16:32:36 -0500 (EST) (envelope-from green@green.homeunix.org) Received: from localhost (green@localhost)i1LLWa7P057630; Sat, 21 Feb 2004 16:32:36 -0500 (EST) Message-Id: <200402212132.i1LLWa7P057630@green.homeunix.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: mckusick@FreeBSD.org, fs@FreeBSD.org From: Brian Fundakowski Feldman Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Feb 2004 16:32:36 -0500 Sender: green@green.homeunix.org Subject: SoftUpdates/fsck considered harmful 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, 21 Feb 2004 21:32:37 -0000 I lost some data which was important to me (thankfully, not lost completely, as a fgrep on the hard disk was able to find a copy) because of a crash while SoftUpdates had some data not yet flushed. I simply had done this: 1. vi file 2. *edit edit edit, :wq* 3. ci file 4. co -l file That should have left me with several copies of it, but when the system panicked, upon reboot fsck told me: Feb 19 21:34:46 green fsck: /dev/ad0s2e: UNREF FILE I=448021 OWNER=green MODE=100644 Feb 19 21:34:46 green fsck: /dev/ad0s2e: SIZE=6298 MTIME=Feb 19 20:38 2004 (CLEARED) I'm certain this was the file I was editing. SoftUpdates only guarantees the disk is in a valid state, not that I won't lost files, but if fsck hadn't decided that "UNREF" meant "the user did not intend this file to exist any longer", I would have had a copy of it in /home/lost+found! Can there please be a less harmful behavior than simply not restoring unlinked files just because they appear to be "UNREF"? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-fs@FreeBSD.ORG Sat Feb 21 14:49:04 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 A9D2F16A4CE for ; Sat, 21 Feb 2004 14:49:04 -0800 (PST) Received: from web40803.mail.yahoo.com (web40803.mail.yahoo.com [66.218.78.180]) by mx1.FreeBSD.org (Postfix) with SMTP id 9B1D143D1F for ; Sat, 21 Feb 2004 14:49:04 -0800 (PST) (envelope-from gustavofukao@yahoo.com) Message-ID: <20040221224904.94103.qmail@web40803.mail.yahoo.com> Received: from [200.153.159.81] by web40803.mail.yahoo.com via HTTP; Sat, 21 Feb 2004 14:49:04 PST Date: Sat, 21 Feb 2004 14:49:04 -0800 (PST) From: Gustavo Fukao To: freebsd-fs@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Problem 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, 21 Feb 2004 22:49:04 -0000 I need substitute mntent.h on FreeBSD 5.2 to compile a program well ------------------------------------------------------------------------------------------------------------ #include #include #include #ifdef __SOLARIS__# include # include #else# include #endif#include #include #include "../include/string.h"#include "../include/fio.h"#include "../include/disk.h"#include "edvtypes.h"#include "edvdevices.h"#include "edvdevicesfio.h"#include "config.h"void EDVDevicesListLoadFromSystem( edv_device_struct ***list, gint *total, gint (*progress_cb)(gpointer, gulong, gulong), gpointer client_data);void EDVDevicesListUpdateMountStatesFromSystem( edv_device_struct **list, gint total);void EDVDevicesListLoadFromFile( const gchar *filename, edv_device_struct ***list, gint *total, gint (*progress_cb)(gpointer, gulong, gulong), gpointer client_data);void EDVDeviceListSaveToFile( const gchar *filename, edv_device_struct **list, gint total, gint (*progress_cb)(gpointer, gulong, gulong), gpointer client_data);#define ATOI(s) (((s) != NULL) ? atoi(s) : 0)#define ATOL(s ) (((s) != NULL) ? atol(s) : 0)#define ATOF(s) (((s) != NULL) ? atof(s) : 0.0f)#define STRDUP(s) (((s) != NULL) ? g_strdup(s) : NULL)#define MAX(a,b) (((a) > (b)) ? (a) : (b))#define MIN(a,b) (((a) < (b)) ? (a) : (b))#define CLIP(a,l,h) (MIN(MAX((a),(l)),(h)))#define STRLEN(s) (((s) != NULL) ? strlen(s) : 0)#define STRISEMPTY(s) (((s) != NULL) ? (*(s) == '\0') : TRUE)/* * Loads devices found in the system (/etc/fstab) list of devices * and appends them to the list. */void EDVDevicesListLoadFromSystem( edv_device_struct ***list, gint *total, gint (*progress_cb)(gpointer, gulong, gulong), gpointer client_data){ FILE *fp; gulong file_size; gint dev_num = -1; edv_device_struct *dev_ptr = NULL;#ifdef __SOLARIS__ struct vfstab *vfs_ptr = NULL; int mtback;#else struct mntent *mt_ptr;#endif struct stat stat_buf; if((list == NULL) || (total == NULL)) return; /* Open system devices list file */#ifdef __SOLARIS__ fp = FOpen("/etc/vfstab", "rb" );#else fp = setmntent("/etc/fstab", "rb");#endif if(fp == NULL) return; /* Get file statistics */ if(fstat(fileno(fp), &stat_buf)) file_size = 0; else file_size = stat_buf.st_size; /* Call progress callback */ if(progress_cb != NULL) progress_cb( client_data, 0, file_size ); /* Begin reading system devices list file */#ifdef __SOLARIS__ vfs_ptr = (struct vfstab *)g_malloc(sizeof(struct vfstab)); mtback = getvfsent(fp, vfs_ptr); while(mtback != 0)#else mt_ptr = getmntent(fp); while(mt_ptr != NULL)#endif { /* Call progress callback */ if(progress_cb != NULL) { if(progress_cb( client_data, (gulong)ftell(fp), file_size )) break; } /* Check if an existing device already exists in * the list that matches the device_path */ dev_ptr = EDVDeviceListMatchDevicePath( *list, *total, &dev_num, mt_ptr->mnt_fsname ); if(dev_ptr == NULL) { /* No existing device structure exists that matches the * device path, so cr eate a new one */ dev_num = *total; *total = dev_num + 1; *list = (edv_device_struct **)g_realloc( *list, (*total) * sizeof(edv_device_struct *) ); if(*list == NULL) { *total = 0; dev_num = -1; dev_ptr = NULL; break; } else { (*list)[dev_num] = dev_ptr = EDVDeviceNew(#ifdef __SOLARIS__ EDVDeviceGetFSFromString(vfs_ptr->vfs_fstype), NULL, vfs_ptr->vfs_special, vfs_ptr->vfs_mountp#else EDVDeviceGetFSFromString(mt_ptr->mnt_type), NULL, mt_ptr->mnt_fsname, mt_ptr->mnt_dir#endif ); if(dev_ptr == NULL) { dev_num = -1; break; } /* Set other default values for this new device */ /* Default icons */ if(EDV_DEVICE_TOTAL_ICON_STATES >= 1) { /* Small icon? */ if(dev_ptr->small_icon_file[0] == NULL) { dev_ptr->small_icon_file[0] = STRDUP( EDV_DEF_DEVICE_ICON_SMALL_FILE ); } /* Medium icon? */ if(dev_ptr->medium_icon_file[0] == NULL) { dev_ptr->medium_icon_file[0] = STR DUP( EDV_DEF_DEVICE_ICON_MEDIUM_FILE ); } /* Large icon? */ if(dev_ptr->large_icon_file[0] == NULL) { dev_ptr->large_icon_file[0] = STRDUP( EDV_DEF_DEVICE_ICON_LARGE_FILE ); } } /* Default fsck program */ g_free(dev_ptr->command_check); dev_ptr->command_check = g_strdup_printf( "%s %s", EDV_DEF_FSCK_FRONT_PROGRAM,#ifdef __SOLARIS__ vfs_ptr->vfs_special#else mt_ptr->mnt_fsname#endif ); /* Default format program */ g_free(dev_ptr->command_format); dev_ptr->command_format = g_strdup_printf( "%s %s", EDV_DEF_FORMAT_FRONT_PROGRAM,#ifdef __SOLARIS__ vfs_ptr->vfs_special#else mt_ptr->mnt_fsname#endif ); } } else { /* Existing device structure exists that matches the * device path, so update its values. */ /* File system type */#ifdef __SOLARIS__ dev_ptr->fs_type = EDVDeviceGetFSFromString(vfs_ptr->vfs_fstype);#else dev_ptr->fs_type = EDVDeviceGetFSFromString(mt_ptr->mnt_type );#endif /* Mount path */#ifdef __SOLARIS__ if(vfs_ptr->vfs_mountp != NULL)#else if(mt_ptr->mnt_dir != NULL)#endif { g_free(dev_ptr->mount_path);#ifdef __SOLARIS__ dev_ptr->mount_path = STRDUP(vfs_ptr->vfs_mountp);#else dev_ptr->mount_path = STRDUP(mt_ptr->mnt_dir);#endif } } /* Read next mount entry */#ifdef __SOLARIS__ mtback = getmntent(fp, vfs_ptr);#else mt_ptr = getmntent(fp);#endif } /* Close system devices list file */#ifdef __SOLARIS__ FClose(fp); fp = NULL; vfs_ptr = NULL;#else endmntent(fp); fp = NULL; mt_ptr = NULL;#endif /* Call progress callback */ if(progress_cb != NULL) progress_cb( client_data, file_size, file_size );}/* * Updates all device structures in the given list by checking if * they are actually mounted on the system. */void EDVDevicesListUpdateMountStatesFromSystem( edv_device_struct **list, gint total){ FILE *fp; gint dev_num = -1; edv_device_struct *dev_ptr = NULL;#ifdef __SOLARIS__ struct mnttab *mt_ptr = NULL; int mtback;#else struct mntent *mt_ptr;#endif if((list == NULL) || (total <= 0)) return; /* Reset mount states on all device structures */ for(dev_num = 0; dev_num < total; dev_num++) { dev_ptr = list[dev_num]; if(dev_ptr == NULL) continue; dev_ptr->is_mounted = FALSE; } /* Open system mounted devices list file */#ifdef __SOLARIS__ fp = FOpen("/etc/mnttab", "rb");#else fp = setmntent("/etc/mtab", "rb");#endif if(fp == NULL) return; /* Begin reading system devices list file */#ifdef __SOLARIS__ mt_ptr = (struct mnttab *)g_malloc(sizeof(struct mnttab)); mtback = getmntent(fp, mt_ptr); while(mtback != 0)#else mt_ptr = getmntent(fp); while(mt_ptr != NULL)#endif { /* Check if this device is in the list */ dev_ptr = EDVDeviceListMatchDevicePath( list, total,#ifdef __SOLARIS__ &dev_num, mt_ptr->mnt_special#else &dev_num, mt_ptr->mnt_fsname#endif ); if(dev_ptr != NULL) { /* Device path of entry from system matches one of the * device struct ures, so mark the device structure as * being mounteded. */ dev_ptr->is_mounted = TRUE; } /* Read next mount entry */#ifdef __SOLARIS__ mtback = getmntent(fp, mt_ptr);#else mt_ptr = getmntent(fp);#endif } /* Close system mounted devices list file */#ifdef __SOLARIS__ FClose(fp); fp = NULL; mt_ptr = NULL;#else endmntent(fp); fp = NULL; mt_ptr = NULL;#endif}/* * Appends the devices found in the specified file to the given * list, updates any existing devices in the list if their * device_path match. */void EDVDevicesListLoadFromFile( const gchar *filename, edv_device_struct ***list, gint *total, gint (*progress_cb)(gpointer, gulong, gulong), gpointer client_data){ gchar *parm_str; FILE *fp; gulong file_size; gint dev_num = -1; edv_device_struct *dev_ptr = NULL; struct stat stat_buf; if((list == NULL) || (total == NULL) || STRISEMPTY(filename)) return; /* Open devices file */ fp = FOpen(filename, "rb"); if(fp == NULL) return; /* Get file statistics */ if(fstat(fileno(fp), &stat_buf)) file_size = 0l; else file_size = (gulong)stat_buf.st_size; /* Call progress callback */ if(progress_cb != NULL) progress_cb( client_data, 0l, file_size ); /* Begin file */ parm_str = NULL; while(TRUE) { /* Call progress callback */ if(progress_cb != NULL) { if(progress_cb( client_data, (gulong)ftell(fp), file_size )) break; } /* Read next parameter */ parm_str = FSeekNextParm( fp, parm_str, EDV_CFG_COMMENT_CHAR, EDV_CFG_DELIMINATOR_CHAR ); if(parm_str == NULL) break; /* Begin handling by parameter */ /* Start of a device block? */ if(!g_strcasecmp(parm_str, "BeginDevice")) { gchar *device_path = FGetString(fp); /* Check if an existing device already exists in * the list that matches the device_path */ dev_ptr = EDVDeviceListMatchDevicePath( *list, *total, &dev_num, device_path ); if(dev_ptr == NULL) { /* No existing device structure exist s that matches * the given device_path, so create a new one */ dev_num = *total; *total = dev_num + 1; *list = (edv_device_struct **)g_realloc( *list, (*total) * sizeof(edv_device_struct *) ); if(*list == NULL) { *total = 0; dev_num = -1; dev_ptr = NULL; } else { (*list)[dev_num] = dev_ptr = EDVDeviceNew( EDV_FS_TYPE_EMPTY, NULL, device_path, NULL ); if(dev_ptr == NULL) { dev_num = -1; } } } } /* File system type? */ else if(!g_strcasecmp(parm_str, "FSType") && (dev_ptr != NULL) ) { gint value[1]; FGetValuesI(fp, value, 1); dev_ptr->fs_type = value[0]; } /* No unmount? */ else if(!g_strcasecmp(parm_str, "NoUnmount") && (dev_ptr != NULL) ) { gint value[1]; FGetValuesI(fp, value, 1); dev_ptr->no_unmount = (gboolean)value[0]; } /* Always mount read only? */ else if(!g_strcasecmp(parm_str, "ReadOnly") && (dev_ptr != NULL) ) { gint value[1]; FGetValuesI(fp, value, 1); dev_ptr->read_only = (gboolean)value[0]; } /* Unlisted? */ else if(!g_strcasecmp(parm_str, "Unlisted") && (dev_ptr != NULL) ) { gint value[1]; FGetValuesI(fp, value, 1); dev_ptr->unlisted = (gboolean)value[0]; } /* Descriptive name? */ else if(!g_strcasecmp(parm_str, "Name") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->name); dev_ptr->name = STRDUP(value); g_free(value); } /* Device mount path? */ else if(!g_strcasecmp(parm_str, "MountPath") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->mount_path); dev_ptr->mount_path = STRDUP(value); g_free(value); } /* Device mount command? */ else if(!g_strcasecmp(parm_str, "CommandMount") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->command_mount); dev_ptr->command_mount = STRDUP(value); g_free(val ue); } /* Device unmount command? */ else if(!g_strcasecmp(parm_str, "CommandUnmount") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->command_unmount); dev_ptr->command_unmount = STRDUP(value); g_free(value); } /* Device eject command? */ else if(!g_strcasecmp(parm_str, "CommandEject") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->command_eject); dev_ptr->command_eject = STRDUP(value); g_free(value); } /* Device check command? */ else if(!g_strcasecmp(parm_str, "CommandCheck") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->command_check); dev_ptr->command_check = STRDUP(value); g_free(value); } /* Device tools command? */ else if(!g_strcasecmp(parm_str, "CommandTools") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->command_tools); dev_ptr->command_tools = STRDUP(value); g_free(value); } /* Device format command? */ else if(!g_strcasecmp(parm_str, "CommandFormat") && (dev_ptr != NULL) ) { gchar *value = FGetString(fp); g_free(dev_ptr->command_format); dev_ptr->command_format = STRDUP(value); g_free(value); } /* Device small icon standard? */ else if(!g_strcasecmp(parm_str, "IconSmallStandard") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->small_icon_file[ EDV_DEVICE_ICON_STATE_STANDARD ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device small icon selected? */ else if(!g_strcasecmp(parm_str, "IconSmallSelected") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->small_icon_file[ EDV_DEVICE_ICON_STATE_SELECTED ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device small icon unmounted? */ else if(!g_strcasecmp(parm_str, "IconSmallUnmounted") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->small_icon_file[ EDV_DEVICE_ICON_STATE_UNMOUNTED ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device medium icon standard? */ else if(!g_strcasecmp(parm_str, "IconMediumStandard") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->medium_icon_file[ EDV_DEVICE_ICON_STATE_STANDARD ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device medium icon selected? */ else if(!g_strcasecmp(parm_str, "IconMediumSelected") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->medium_icon_file[ EDV_DEVICE_ICON_STATE_SELECTED ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device medium icon unmounted? */ else if(!g_strcasecmp(parm_str, "IconMediumUnmounted") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->medium_icon_file[ EDV_DEVICE_ICON_STATE_UNMOUNTED ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device large icon standard? */ else if(!g_strcasecmp(parm_str, "IconLargeStandard") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->large_icon_file[ EDV_DEVICE_ICON_STATE_STANDARD ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device large icon selected? */ else if(!g_strcasecmp(parm_str, "IconLargeSelected") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->large_icon_file[ EDV_DEVICE_ICON_STATE_SELECTED ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* Device large icon unmounted? */ else if(!g_strcasecmp(parm_str, "IconLargeUnmounted") && (dev_ptr != NULL) ) { gchar *path = FGetString(fp); gchar **storage = &dev_ptr->large_icon_file[ EDV_DEVICE_ICON_STATE_UNMOUNTED ]; g_free(*storage); *storage = STRDUP(path); g_free(path); } /* End of a device block? */ else if(!g_strcasecmp(parm_str, "EndDevice")) { FSeekNextLine(fp); /* Reset contexts */ dev_num = -1; dev_ptr = NULL; } /* All else unsupported parameter or wrong context */ else { FSeekNextLine(fp); } } /* Delete parameter */ g_free(parm_str); /* Close devices file */ FClose(fp);}/* * Saves the given list of devices to file. */void EDVDeviceListSaveToFile( const gchar *filename, edv_device_struct **list, gint total, gint (*progress_cb)(gpointer, gulong, gulong), gpointer client_data){ gint dev_num; const edv_device_struct *dev_ptr; gchar *parent_path; FILE *fp; const gchar *path; if((list == NULL) || STRISEMPTY(filename)) return; /* Get parent directory and create it as needed */ parent_path = STRDUP(GetParentDir(filename)); if(parent_path != NULL) { rmkdir(parent_path, S_IRUSR | S_IWUSR | S_IXUSR); g_free(parent_path); parent_path = NULL; } /* Open devices file for writing */ fp = FOpen(filename, "wb"); if(fp == NULL) return; /* Call progress callback */ if(progress_cb != NULL) progress_cb( client_data, 0l, (gulong)total ); /* Iterate through all device structures */ for(dev_num = 0; dev_num < total; dev_num++) { dev_ptr = list[dev_num]; if(dev_ptr == NULL) continue; /* Skip devices that are marked internal, meaning they * should not be saved to file */ if(dev_ptr->internal) continue; /* Call progress callback */ if(progress_cb != NULL) { if(progress_cb( client_data, (gulong)(dev_num + 1), (gulong)total )) break; } /* Begin writing device block */ fprintf( fp, "BeginDevice = %s\n", dev_ptr->device_path ); /* File system type */ fprintf( fp, " FSType = %i\n", dev_ptr->fs_type ); /* No unmount */ fprintf( fp, " NoUnmount = %i\n", dev_ptr->no_unmount ); /* Always mount read only */ fprintf( fp, " ReadOnly = %i\n", dev_ptr->read_only ); /* Unlisted */ fprintf( fp, " Unlisted = %i\n", dev_ptr->unlisted ); /* Descriptive name */ if(dev_ptr->name != NULL) fprintf( fp, " Name = %s\n", dev_ptr->name ); /* Mount path */ if(dev_ptr->mount_path != NULL) fprintf( fp, " MountPath = %s\n", dev_ptr->mount_path ); /* Mount command */ if(dev_ptr->command_mount != NULL) fprintf( fp, " CommandMount = %s\n", dev_ptr->command_mount ); /* Unmount command */ if(dev_ptr->command_unmount != NULL) fprintf( fp, " CommandUnmount = %s\n", dev_ptr->command_unmount ); /* Eject command */ if(dev_ptr->command_eject != NULL) fprintf( fp, " CommandEject = %s\n", dev_ptr->command_eject ); /* Device check command */ if(dev_ptr->command_check != NULL) fprintf( fp, " CommandCheck = %s\n", dev_ptr->command_check ); /* Device tools command */ if(dev_ptr->command_tools != NULL) fprintf( fp, " CommandTools = %s\n", dev_ptr->command_tools ); /* Device format command */ if(dev_ptr->command_format != NULL) fprintf( fp, " CommandFormat = %s\n", dev_ptr->command_format ); /* Icon small standard file */ path = dev_ptr->small_icon_file[EDV_DEVICE_ICON_STATE_STANDARD]; if(path != NULL) fprintf( fp, " IconSmallStandard = %s\n", path ); /* Icon small selected file */ path = dev_ptr->small_icon_file[EDV_DEVICE_ICON_STATE_SELECTED]; if(path != NULL) fprintf( fp, " IconSmallSelected = %s\n", path ); /* Icon small unmounted file */ path = dev_ptr->small_icon_file[EDV_DEVICE_ICON_STATE_UNMOUNTED]; if(path != NULL) fprintf( fp, " IconSmallUnmoun ted = %s\n", path ); /* Icon medium standard file */ path = dev_ptr->medium_icon_file[EDV_DEVICE_ICON_STATE_STANDARD]; if(path != NULL) fprintf( fp, " IconMediumStandard = %s\n", path ); /* Icon medium selected file */ path = dev_ptr->medium_icon_file[EDV_DEVICE_ICON_STATE_SELECTED]; if(path != NULL) fprintf( fp, " IconMediumSelected = %s\n", path ); /* Icon medium unmounted file */ path = dev_ptr->medium_icon_file[EDV_DEVICE_ICON_STATE_UNMOUNTED]; if(path != NULL) fprintf( fp, " IconMediumUnmounted = %s\n", path ); /* Icon large standard file */ path = dev_ptr->large_icon_file[EDV_DEVICE_ICON_STATE_STANDARD]; if(path != NULL) fprintf( fp, " IconLargeStandard = %s\n", path ); /* Icon large selected file */ path = dev_ptr->large_icon_file[EDV_DEVICE_ICON_STATE_SELECTED]; if(path != NULL) fprintf( fp, " IconLargeSelected = %s \n", path ); /* Icon large unmounted file */ path = dev_ptr->large_icon_file[EDV_DEVICE_ICON_STATE_UNMOUNTED]; if(path != NULL) fprintf( fp, " IconLargeUnmounted = %s\n", path ); /* End device block */ fprintf( fp, "EndDevice\n" ); } /* Close devices file */ FClose(fp);} ------------------------------------------------------------------------------------------------------------ Anyone Can help me ??? Thank to the attenrion Gustavo Fukao FreeBSD user http://www.freebsd-br.cjb.net --------------------------------- Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. From owner-freebsd-fs@FreeBSD.ORG Sat Feb 21 14:53:16 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 2928116A4CE for ; Sat, 21 Feb 2004 14:53:16 -0800 (PST) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56E1643D1D for ; Sat, 21 Feb 2004 14:53:15 -0800 (PST) (envelope-from tilman@arved.at) Received: from huckfinn-wi0.arved.de (localhost [127.0.0.1]) i1LMrCcj023241; Sat, 21 Feb 2004 23:53:14 +0100 (CET) (envelope-from tilman@arved.at) Received: (from tilman@localhost) by huckfinn-wi0.arved.de (8.12.11/8.12.6/Submit) id i1LMrCTQ023240; Sat, 21 Feb 2004 23:53:12 +0100 (CET) X-Authentication-Warning: huckfinn-wi0.arved.de: tilman set sender to tilman@arved.at using -f Date: Sat, 21 Feb 2004 23:53:12 +0100 From: Tilman Linneweh To: Gustavo Fukao Message-ID: <20040221225312.GA23211@huckfinn.arved.de> References: <20040221224904.94103.qmail@web40803.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040221224904.94103.qmail@web40803.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-fs@FreeBSD.org Subject: Re: Problem 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, 21 Feb 2004 22:53:16 -0000 * Gustavo Fukao [Sa, 21 Feb 2004 at 23:49 GMT]: > I need substitute > > mntent.h on FreeBSD 5.2 to compile a program > well Take a look at the devel/fam port. It has a mntent.h wrapper. regards tilman