From owner-freebsd-fs@FreeBSD.ORG Sun Feb 4 02:37:22 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0ADE016A403 for ; Sun, 4 Feb 2007 02:37:22 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from mailhost.tao.org.uk (transwarp.tao.org.uk [87.74.4.34]) by mx1.freebsd.org (Postfix) with ESMTP id 9E3CC13C467 for ; Sun, 4 Feb 2007 02:37:21 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from genius.tao.org.uk (wireless58.dhcp.tao.org.uk [87.74.4.58]) by mailhost.tao.org.uk (Postfix) with ESMTP id C4DD36146; Sun, 4 Feb 2007 02:37:19 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 1000) id DE74540D4; Sun, 4 Feb 2007 02:37:11 +0000 (GMT) Date: Sun, 4 Feb 2007 02:37:11 +0000 From: Josef Karthauser To: fs@freebsd.org Message-ID: <20070204023711.GA3393@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: hackers@freebsd.org Subject: nullfs and named pipes. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Feb 2007 02:37:22 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey guys, does anyone know off the top of their heads why named pipes don't appear to work across null_fs mounted partitions? i.e. if I have a named pipe in a file system, # ls -ld /mysql/mysql.sock=20 srwxrwxrwx 1 mysql wheel 0 Feb 3 19:01 /mysql/mysql.sock # mysql --socket=3D/mysql/mysql.sock Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 6 Server version: 5.0.33-log FreeBSD port: mysql-server-5.0.33 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql>=20 However if I make this available elsewhere via a null_fs mount: # mkdir /foo # mount_nullfs /mysql /foo # ls -ld /foo/mysql.sock=20 srwxrwxrwx 1 mysql wheel 0 Feb 3 19:01 /foo/mysql.sock # mysql --socket=3D/foo/mysql.sock -p Enter password:=20 ERROR 2002 (HY000): Can't connect to local MySQL server through socket = '/foo/mysql.sock' (61) the socket stops working. However a hardlink to the socket works: # umount /foo # ln /mysql/mysql.sock /foo/mysql.sock # mysql --socket=3D/foo/mysql.sock Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 10 Server version: 5.0.33-log FreeBSD port: mysql-server-5.0.33 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. Is this a fundamental design issue with null_fs or a bug? There appears to be a lot of confusion on the lists about this point as many people are trying to do this so as to make a single mysql server available from within a number of jails, for instance. However people appear to think that this is a limitation of the jail code, not a limitation of the null_fs code. Having named pipes work in null_fs filesystems would be a very handy thing indeed. I'd appreciate any insights into this. Many thanks, Joe --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iEYEARECAAYFAkXFRtcACgkQXVIcjOaxUBZ2AgCfTJ8HIcdLfntDJMmcX5ndeyDL W5IAoJ+u0qy81TjfB/P1XedupjNxqp+m =5sRm -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn-- From owner-freebsd-fs@FreeBSD.ORG Sun Feb 4 12:13:54 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F08D16A504 for ; Sun, 4 Feb 2007 12:13:54 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 3BE7213C461 for ; Sun, 4 Feb 2007 12:13:53 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id A131845CD9; Sun, 4 Feb 2007 13:13:52 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id DE885456B1; Sun, 4 Feb 2007 13:13:41 +0100 (CET) Date: Sun, 4 Feb 2007 13:12:46 +0100 From: Pawel Jakub Dawidek To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20070204121246.GB69414@garage.freebsd.pl> References: <45C4C478.1000003@quip.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Content-Disposition: inline In-Reply-To: <45C4C478.1000003@quip.cz> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.org Subject: Re: unreadable (pending) sectors X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Feb 2007 12:13:54 -0000 --s/l3CgOIzMHHjg/5 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 03, 2007 at 06:20:56PM +0100, Miroslav Lachman wrote: > Hi all, >=20 > a few days ago I start reading records like this in /var/log/messages >=20 > Feb 3 17:27:22 roxy smartd[71846]: Device: /dev/ad6, 1 Currently unreada= ble (pending) sectors > Feb 3 17:27:22 roxy smartd[71846]: Device: /dev/ad6, 1 Offline uncorrect= able sectors >=20 > ad6 is one of two drives in gmirror, so I am not so "scared" ;) >=20 > Related parts of output of smartctl -a /dev/ad6 >=20 > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always = - 1 > 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline = - 1 > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always = - 0 > 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always = - 0 > 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always = - 2 >=20 > # 1 Extended offline Completed: read failure 10% 4118 = 474119936 > # 2 Short offline Completed without error 00% 4115 = - >=20 > How can I determine which file belongs to LBA 474119936 / How can I try t= o write to this sector, so drive can internaly realocate this bad sector? > Is there any special tools/commands to this? It will be possible to write such a tool, but I don't know if one already exist... What you want to do (write to bad sectors) should be integral gmirror/graid3 functionality - when error is detected on read, operation is repeated on 2nd half of the mirror and when completed, it should write to the first half. It is not implemented yet, but I'm planning to do so. This also have a nice additional value. You can configure geli authentication on top of each mirror half and when silent data corruption is detected by geli, gmirror will read data from the other half and rewrite corrupted region with correct data. Almost like ZFS:) What I can suggest now is to just rebuild the problematic half: # gmirror rebuild ad6 --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --s/l3CgOIzMHHjg/5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFxc2+ForvXbEpPzQRAi9OAKCBnsWJq5L+CHyk8pLL0tw+Tm5BRwCfTiuJ J4cHUo93uE9bdR7Hx17p+uA= =5vNQ -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5-- From owner-freebsd-fs@FreeBSD.ORG Sun Feb 4 22:36:49 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7EFD16A409 for ; Sun, 4 Feb 2007 22:36:49 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from smtp.voda.cz (gw.voda.cz [212.24.154.90]) by mx1.freebsd.org (Postfix) with ESMTP id 6C63113C4AA for ; Sun, 4 Feb 2007 22:36:49 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from localhost (localhost [127.0.0.1]) by smtp.voda.cz (Postfix) with ESMTP id 8937B4378E for ; Sun, 4 Feb 2007 23:12:03 +0100 (CET) Received: from smtp.voda.cz ([127.0.0.1]) by localhost (mail.voda.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08286-04 for ; Sun, 4 Feb 2007 23:12:00 +0100 (CET) Received: from spyro.eiecon.net (unknown [213.151.77.190]) by smtp.voda.cz (Postfix) with ESMTP id 9CDE743783 for ; Sun, 4 Feb 2007 23:11:59 +0100 (CET) Date: Sun, 04 Feb 2007 23:11:59 +0100 To: freebsd-fs@freebsd.org From: Indigo Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-2 MIME-Version: 1.0 References: Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: User-Agent: Opera Mail/9.10 (Win32) X-Virus-Scanned: by amavisd-new at voda.cz Subject: Dumb filesystem idea X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Feb 2007 22:36:49 -0000 Hello Everyone, Im about to try a disklayout experiment and I wanted to ask everyone if Im trying things that are pointless or if I should extend the experiment somehow. Hardware: Highpoint RocketRAID 2320 2xWD Raptor 74GB 5xWD Caviar 320GB Original idea for the setup: 74GB RAID1 (Raptors) /,/var,/usr 50GB RAID0 (Caviars[10GB from each - maybe less]) swap,/usr/obj,/tmp,[/var/audit] 1TB+ RAID5 (Caviars[the rest]) /home (or just general storage) The goal is to waste as few fast/reliable space as possible on things that CAN be lost and to generally reorganize the filesystem by file purpose. Known issue is that I'll need some script to recreate the RAID0 filesystems when they crash. Am I onto something here? I feel like running in circles - it's dumb to put /var/obj on the RAID1 where it just eats valuable space. But it's also dumb to put things on a RAID0 where they will crash a running system in the event of disk failure. I know my idea won't work but I wanted to ask if anyone was playing with similar ideas. Thanks, Vasek From owner-freebsd-fs@FreeBSD.ORG Mon Feb 5 05:01:46 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 562FA16A400 for ; Mon, 5 Feb 2007 05:01:46 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id E8A1413C4A5 for ; Mon, 5 Feb 2007 05:01:45 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1957449nfc for ; Sun, 04 Feb 2007 21:01:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=fZNvS+x+YiPT/Md46oMD3jGA+TojuE0LQyCPVp45fdjUxWpEwI//hmUwWvXinYNnk5Ut25KK7++sph9msztZA5Kc1/lT1cPTmAXQyPSWPTRuCvSJN6/IoHpVvbiLBUabCHigdqfFVrhofqu9dCrB+ArLwzubmubzLvxnn0uo7Gw= Received: by 10.49.29.3 with SMTP id g3mr1745951nfj.1170650072974; Sun, 04 Feb 2007 20:34:32 -0800 (PST) Received: by 10.48.162.13 with HTTP; Sun, 4 Feb 2007 20:34:32 -0800 (PST) Message-ID: <440b3e930702042034w5e5879e3r8b76dc1971ad90fd@mail.gmail.com> Date: Sun, 4 Feb 2007 23:34:32 -0500 From: "Ali Mashtizadeh" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: UDF Bug X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 05:01:46 -0000 SXQgc2VlbXMgSSBoYXZlIGEgYnVnIHdpdGggYSBVREYgRFZEK1Igb24gNi4yLVJFTEVBU0UuIE15 IGNvbXB1dGVyIHdvcmtlZApmaW5lIHdoZW4gSSBjb3BpZWQgdGhlIGZpbGUgZnJvbSB0aGUgZGlz YyBpbiB0aGUgY29uc29sZS4gTGF0ZXIgSSB0cmllZCB0bwphY2Nlc3MgdGhlIHNhbWUgZmlsZSBv biB0aGUgRFZEIGFuZCBpdCByZWJvb3RlZCB3aGVuIEkgd2FzIGluIFggd2luZG93cy4KQW55b25l IGhhdmUgYSBzaW1pbGFyIGV4cGVyaWVuY2UuIEkgY291bGRuJ3QgZ2V0IGRlYnVnZ2luZyBpbmZv cm1hdGlvbiBvbiBpdAp5ZXQgdGhvdWdoIDooLiBUaGUgb25seSB0aGluZ3MgdGhhdCB3ZXJlIGRp ZmZlcmVudCBiZXR3ZWVuIHRoZSB0d28gYWNjZXNzJ3MKdGhlIHNlY29uZCB0aW1lIEkgaGFkIG1v dW50ZWQgc2V2ZXJhbCBORlMgc2hhcmVzIGFuZCB3YXMgaW4gWCB3aW5kb3dzLgoKUG9zc2libHkg dGhpcyBjb3VsZCBiZSBkdWUgdG8gc2NyYXRjaGVzIG9uIHRoZSBkaXNrPyBUaGVyZSB3ZXJlIGEg Y291cGxlCnNtYWxsIHNjcmF0Y2hlcyBidXQgd2h5IHdvdWxkIGl0IHdvcmsgb24gaW5pdGlhbCBi b290IHVwIGFuZCBjb25zaXN0ZW50bHkKY3Jhc2ggaW4geC13aW5kb3dzPyBJIGhhdm4ndCBzZWVu IHRoaXMgYmVmb3JlIGJ1dCB0aGlzIGlzIG15IGZpcnN0IHVzYWdlIG9mClVERiBzaW5jZSBJIHVw Z3JhZGVkIGFsbCBteSBtYWNoaW5lcyB0byA2LjItUkVMRUFTRS4KClRoZSBvbmx5IHJlbGF0ZWQg YnVnIHJlcG9ydCBJIGZvdW5kIGlzIHRoaXM6Cmh0dHA6Ly93d3cuZnJlZWJzZC5vcmcvY2dpL3F1 ZXJ5LXByLmNnaT9wcj02MzMwNSAtIEl0J3MgY2xvc2VkIHRob3VnaAoKSG9wZWZ1bGx5IEkgY2Fu IGxvb2sgaW50byB0aGlzIG1vcmUgYW5kIHByb3ZpZGUgc29tZSBraW5kIG9mIGRlYnVnZ2luZwpp bmZvcm1hdGlvbiBpcyBhbnlvbmUgaGFzIHN1Z2dlc3Rpb25zIG9yIGhhcyBleHBlcmllbmNlZCB0 aGUgc2FtZSB0aGluZy4KCi0tIApBbGkgTWFzaHRpemFkZWgK2LnZhNuMINmF2LTYqtuMINiy2KfY r9mHCg== From owner-freebsd-fs@FreeBSD.ORG Mon Feb 5 15:28:49 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E5AC16A402 for ; Mon, 5 Feb 2007 15:28:49 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 8EC4213C467 for ; Mon, 5 Feb 2007 15:28:48 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (dixgpk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l15FSf7c085773; Mon, 5 Feb 2007 16:28:47 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l15FSfsj085766; Mon, 5 Feb 2007 16:28:41 +0100 (CET) (envelope-from olli) Date: Mon, 5 Feb 2007 16:28:41 +0100 (CET) Message-Id: <200702051528.l15FSfsj085766@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG, ticso@cicely.de In-Reply-To: <20070203130226.GO70860@cicely12.cicely.de> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 05 Feb 2007 16:28:47 +0100 (CET) Cc: Subject: Re: Mysterious block count (reproducible) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 15:28:49 -0000 Bernd Walter wrote: > Oliver Fromme wrote: > > [...] > > $ BLOCKSIZE=16K ls -s foo > > 15 foo > > # fsdb -r /dev/md0 > > [...] > > fsdb (inum: 5)> blocks > > Blocks for inode 5: > > Direct blocks: > > 2136, 2144, 2152, 2160, 2168, 2176, 2184, 2192, 2248, 2256, 2264, 2272 > > Indirect blocks: > > 2280, 2288, > > fsdb (inum: 5)> > > > > It lists 12 direct blocks and 2 indirect blocks, that's > > still 14 blocks, not 15. > > > > Where did the 15th block go?!? Or is there a bug in > > the calculation of ls -s output? (Meanwhile I found out that ls(1) doesn't really calculate anything; it simply displays the st_blocks value from the stat structure rounded to $BLOCKSIZE, of course.) > Don't forget the block needed for the indirect table. > fsdb only shows data blocks it seems. Oh, OK ... I really assumed that fsdb would display them as soon as they come into play. :-( What I'm trying to do is to write a small script that calculates the allocation vs. virtual size ratio of sparse files. For that purpose I have to find out how many blocks a file would require if it wasn't sparse. Is there are an easy way to get that information? I have currently hardcoded some information in the script, but it's an ugly hack: http://www.secnetix.de/~olli/scripts/sparsecheck Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "IRIX is about as stable as a one-legged drunk with hypothermia in a four-hundred mile per hour wind, balancing on a banana peel on a greased cookie sheet -- when someone throws him an elephant with bad breath and a worse temper." -- Ralf Hildebrandt From owner-freebsd-fs@FreeBSD.ORG Mon Feb 5 16:48:31 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7403416A408 for ; Mon, 5 Feb 2007 16:48:31 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id E60C313C49D for ; Mon, 5 Feb 2007 16:48:30 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l15GYjVM004120; Mon, 5 Feb 2007 10:34:46 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45C75CA5.5030409@freebsd.org> Date: Mon, 05 Feb 2007 10:34:45 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Indigo References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2525/Mon Feb 5 10:11:08 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: Dumb filesystem idea X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2007 16:48:31 -0000 On 02/04/07 16:11, Indigo wrote: > Hello Everyone, > Im about to try a disklayout experiment and I wanted to ask everyone if > Im trying things that are pointless or if I should extend the experiment > somehow. > > Hardware: > Highpoint RocketRAID 2320 > 2xWD Raptor 74GB > 5xWD Caviar 320GB > > Original idea for the setup: > 74GB RAID1 (Raptors) > /,/var,/usr > 50GB RAID0 (Caviars[10GB from each - maybe less]) > swap,/usr/obj,/tmp,[/var/audit] > 1TB+ RAID5 (Caviars[the rest]) > /home (or just general storage) > > The goal is to waste as few fast/reliable space as possible on things that > CAN be lost and to generally reorganize the filesystem by file purpose. > > Known issue is that I'll need some script to recreate the RAID0 > filesystems when they crash. > > Am I onto something here? I feel like running in circles - it's dumb to > put /var/obj on the RAID1 where it just eats valuable space. But it's also > dumb to put things on a RAID0 where they will crash a running system in > the event of disk failure. I know my idea won't work but I wanted to ask > if anyone was playing with similar ideas. It's not dumb - there's even been some lengthy discussion of this on the freebsd-geom@ list recently I believe. Check the archives, and you can read up on nearly this exact scenario. Eric From owner-freebsd-fs@FreeBSD.ORG Tue Feb 6 06:48:29 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F4F016A401 for ; Tue, 6 Feb 2007 06:48:29 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id B29A613C46B for ; Tue, 6 Feb 2007 06:48:28 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so72010nfc for ; Mon, 05 Feb 2007 22:48:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=QkBplrKN1CyadQSS+OOEPQPiAbl8ybCQOwuhLdOkSEo0Jp1TfaP+6Kp1KkQaxANCUcjgGpvSOSa5gzVA2vXcjKpCE6JSLbxqFUtbLjEaj2As+H2iOsW5GfCZr9ntBvYyUjXzD2mu8eC5GKnwgEGFRLgYEPdmXtyUDE/138P88ak= Received: by 10.49.93.4 with SMTP id v4mr134955nfl.1170742856457; Mon, 05 Feb 2007 22:20:56 -0800 (PST) Received: by 10.49.27.4 with HTTP; Mon, 5 Feb 2007 22:20:56 -0800 (PST) Message-ID: Date: Tue, 6 Feb 2007 09:20:56 +0300 From: pluknet To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: incorrect(?) errno value in msdosfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 06:48:29 -0000 hello. I have discovered an unexpected behavior. If I perform a search operation in the directory for non-existing files, then I get the EINVAL value on msdosfs filesystem instead of the ENOENT value returned. Actually I don't know what is the right value should be returned and thus maybe I'm wrong and I'm sorry for annoying. But It simply differs from the value normally returned on ufs2 filesystem. So I decide to write here. :) It is observed on 6.2 and CURRENT. For example if I run the next command on msdosfs filesystem, this is what I get: bash-2.05b$ ls /mnt/msdosfs/*.nonexistent ls: /mnt/msdosfs/*.nonexistent: Invalid argument instead of: bash-2.05b$ ls /mnt/msdosfs/*.nonexistent ls: /mnt/msdosfs/*.nonexistent: No such file or directory This behavior is fixed with the next workaround in v1.47, but I guess that perhaps it needs to fix in some another place. bash-2.05b$ diff -u -p msdosfs_lookup.c.orig msdosfs_lookup.c --- msdosfs_lookup.c.orig Tue Feb 6 08:56:43 2007 +++ msdosfs_lookup.c Tue Feb 6 08:59:42 2007 @@ -147,7 +147,7 @@ msdosfs_lookup(ap) switch (unix2dosfn((const u_char *)cnp->cn_nameptr, dosfilename, cnp->cn_namelen, 0, pmp)) { case 0: - return (EINVAL); + return (ENOENT); case 1: break; case 2: wbr, pluknet From owner-freebsd-fs@FreeBSD.ORG Tue Feb 6 07:52:51 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C33616A403; Tue, 6 Feb 2007 07:52:51 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id DCAE813C474; Tue, 6 Feb 2007 07:52:50 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (cxinax@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l167qikS068392; Tue, 6 Feb 2007 08:52:49 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l167qhup068391; Tue, 6 Feb 2007 08:52:43 +0100 (CET) (envelope-from olli) Date: Tue, 6 Feb 2007 08:52:43 +0100 (CET) Message-Id: <200702060752.l167qhup068391@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, pluknet@gmail.com In-Reply-To: X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 06 Feb 2007 08:52:49 +0100 (CET) Cc: Subject: Re: incorrect(?) errno value in msdosfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, pluknet@gmail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 07:52:51 -0000 pluknet wrote: > I have discovered an unexpected behavior. If I perform a search > operation in the directory for non-existing files, then I get > the EINVAL value on msdosfs filesystem instead of > the ENOENT value returned. EINVAL should be returned if you try to lookup an invalid file name. ENOENT should be returned if the file name is valid but does not exist. Remember that MSDOSFS is a lot stricter than UFS, as far as valid file names are concerned. For example, the only characters forbidden in UFS file names are '/' (slash) and '\0' (zero byte), because slash is the directory separator and zero byte is the string terminator. On the other hand, quite a lot of characters are not allowed in MSDOSFS file names, including the wildcards '?' and '*'. > For example if I run the next command on msdosfs filesystem, > this is what I get: > > bash-2.05b$ ls /mnt/msdosfs/*.nonexistent > ls: /mnt/msdosfs/*.nonexistent: Invalid argument That's correct behaviour. Let me explain: When your shell encounters unquoted wildcards ('*' in this case), it retrieves a directory listing and tries to match the entries with your pattern. If there is no match, the default behaviour of most bourne-compatible shells (including bash) is to use the pattern as-is, i.e. as if it was quoted. In other words, it tries to look for a literal file name of "*.nonexistent". As I explained above, the '*' character is illegal in MSDOSFS file names, so the lookup function returns EINVAL without even trying to locate that file name in the directory. > instead of: > > bash-2.05b$ ls /mnt/msdosfs/*.nonexistent > ls: /mnt/msdosfs/*.nonexistent: No such file or directory That would be incorrect behaviour. Try to look up a file name that's valid (but doesn't exist either). You will certainly get ENOENT. If you still get EINVAL, it's time to submit a PR. :-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "And believe me, as a C++ programmer, I don't hesitate to question the decisions of language designers. After a decent amount of C++ exposure, Python's flaws seem ridiculously small." -- Ville Vainio From owner-freebsd-fs@FreeBSD.ORG Tue Feb 6 08:14:40 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 14A2116A400 for ; Tue, 6 Feb 2007 08:14:40 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id A232713C481 for ; Tue, 6 Feb 2007 08:14:39 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so88236nfc for ; Tue, 06 Feb 2007 00:14:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rESWgtAU8T+ycPM+VLXDdmLzvJHjy8eOQkaZp7TO/NVoRXN5tsnSgxdJ7w8V0s1qxRaifzGW74yyu6twn6jHt7C9Dg3uyE5Gu5fVQOmGSw8yBsVr6Q0msntpasYKfdFHQuo623NhcfFOVK7nfoe4JGQ4z9WPRdjSOKBKfIU6dSI= Received: by 10.82.165.1 with SMTP id n1mr1837449bue.1170749677890; Tue, 06 Feb 2007 00:14:37 -0800 (PST) Received: by 10.49.27.4 with HTTP; Tue, 6 Feb 2007 00:14:37 -0800 (PST) Message-ID: Date: Tue, 6 Feb 2007 11:14:37 +0300 From: pluknet To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, pluknet@gmail.com In-Reply-To: <200702060752.l167qhup068391@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200702060752.l167qhup068391@lurza.secnetix.de> Cc: Subject: Re: incorrect(?) errno value in msdosfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 08:14:40 -0000 On 06/02/07, Oliver Fromme wrote: > pluknet wrote: > > I have discovered an unexpected behavior. If I perform a search > > operation in the directory for non-existing files, then I get > > the EINVAL value on msdosfs filesystem instead of > > the ENOENT value returned. > > EINVAL should be returned if you try to lookup an invalid > file name. ENOENT should be returned if the file name is > valid but does not exist. > > Remember that MSDOSFS is a lot stricter than UFS, as far > as valid file names are concerned. For example, the only > characters forbidden in UFS file names are '/' (slash) and > '\0' (zero byte), because slash is the directory separator > and zero byte is the string terminator. On the other hand, > quite a lot of characters are not allowed in MSDOSFS file > names, including the wildcards '?' and '*'. > > > For example if I run the next command on msdosfs filesystem, > > this is what I get: > > > > bash-2.05b$ ls /mnt/msdosfs/*.nonexistent > > ls: /mnt/msdosfs/*.nonexistent: Invalid argument > > That's correct behaviour. Let me explain: > > When your shell encounters unquoted wildcards ('*' in this > case), it retrieves a directory listing and tries to match > the entries with your pattern. If there is no match, the > default behaviour of most bourne-compatible shells > (including bash) is to use the pattern as-is, i.e. as if > it was quoted. In other words, it tries to look for a > literal file name of "*.nonexistent". > > As I explained above, the '*' character is illegal in > MSDOSFS file names, so the lookup function returns EINVAL > without even trying to locate that file name in the > directory. > > > instead of: > > > > bash-2.05b$ ls /mnt/msdosfs/*.nonexistent > > ls: /mnt/msdosfs/*.nonexistent: No such file or directory > > That would be incorrect behaviour. > > Try to look up a file name that's valid (but doesn't exist > either). You will certainly get ENOENT. If you still get > EINVAL, it's time to submit a PR. :-) > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 > Any opinions expressed in this message are personal to the author and may > not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > "And believe me, as a C++ programmer, I don't hesitate to question > the decisions of language designers. After a decent amount of C++ > exposure, Python's flaws seem ridiculously small." -- Ville Vainio > Thanks for the explanation. I have forgotten about a not allowed wildcards :( wbr, pluknet From owner-freebsd-fs@FreeBSD.ORG Tue Feb 6 12:36:57 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F2F216A401; Tue, 6 Feb 2007 12:36:57 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210]) by mx1.freebsd.org (Postfix) with ESMTP id 1050513C4A3; Tue, 6 Feb 2007 12:36:57 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.2.163]) by mailout1.pacific.net.au (Postfix) with ESMTP id D86AC5A0719; Tue, 6 Feb 2007 23:36:45 +1100 (EST) Received: from besplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (Postfix) with ESMTP id 9F03027417; Tue, 6 Feb 2007 23:36:44 +1100 (EST) Date: Tue, 6 Feb 2007 23:36:43 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: pluknet In-Reply-To: Message-ID: <20070206225814.R31484@besplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: incorrect(?) errno value in msdosfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 12:36:57 -0000 On Tue, 6 Feb 2007, pluknet wrote: > I have discovered an unexpected behavior. If I perform a search > operation in the directory for non-existing files, then I get > the EINVAL value on msdosfs filesystem instead of > the ENOENT value returned. Actually I don't know what is > the right value should be returned and thus maybe I'm wrong > and I'm sorry for annoying. But It simply differs from the value > normally returned on ufs2 filesystem. So I decide to write here. :) > It is observed on 6.2 and CURRENT. > > For example if I run the next command on msdosfs filesystem, > this is what I get: > > bash-2.05b$ ls /mnt/msdosfs/*.nonexistent > ls: /mnt/msdosfs/*.nonexistent: Invalid argument > > instead of: > > bash-2.05b$ ls /mnt/msdosfs/*.nonexistent > ls: /mnt/msdosfs/*.nonexistent: No such file or directory This is an annoying difference, but EINVAL is the correct error for msdosfs, since "*" is invalid in msdosfs file names. In general, msdosfs can't always handle things as expected since it can't represent all ffs metadata. Here if you did something like `touch "*.nonexistent"' where the file "*.nonexistent" doesn't exist, then msdosfs would refuse to create the file since "*" is invalid, and ffs would create a file named "*.nonexistent" which is probably not what you want. OTOH, `touch *.nonexistent' might match a file named existent.nonexistent and work right in both cases. > This behavior is fixed with the next workaround in v1.47, > but I guess that perhaps it needs to fix in some another place. Rev,1.46 is about an especially annoying variation of this problem: suppose a file named "Foo" exists. Then lookups and globs of the file by name "foo" and "f*" should succeed, but most parts of the system don't actually understand case insensitive file names so lookups and globs tend to fail. Lookups for open() work but require a full pathname. Rev.1.46 is about the name cache not understanding case insensitive file names (it disables a completely broken part, but I think the name cache can still be thrashed by asking it to cache all 2^N spellings of a file name of length N). fnmatch(3) has a case-insensitive flag, but it doesn't seem to be used by shells (maybe there is a shell option for this). The problem seemed to be just as large using bash under Cygwin under Windows. I have sometimes used the workaround of mounting with -s so that all file names get mapped to lower case and long file names get truncated. Perhaps there should be options to truncate to all lower case or all upper case without truncation. That moves the problem a bit -- after mapping to either case but differently under different OS's, after a while you get an annoying mixture of upper and lower case for new files. IIRC, I used the workaround mainly to reduce the case clobbering on restore from a backup made with different case conventions. Bruce From owner-freebsd-fs@FreeBSD.ORG Tue Feb 6 16:48:31 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8864A16A400; Tue, 6 Feb 2007 16:48:31 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5A42213C481; Tue, 6 Feb 2007 16:48:31 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l16GFkXE054869; Tue, 6 Feb 2007 10:15:47 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45C8A9B2.4090605@freebsd.org> Date: Tue, 06 Feb 2007 10:15:46 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Josef Karthauser References: <20070204023711.GA3393@genius.tao.org.uk> In-Reply-To: <20070204023711.GA3393@genius.tao.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2527/Tue Feb 6 04:14:46 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: hackers@freebsd.org, fs@freebsd.org Subject: Re: nullfs and named pipes. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 16:48:31 -0000 On 02/03/07 20:37, Josef Karthauser wrote: > Hey guys, does anyone know off the top of their heads why named pipes > don't appear to work across null_fs mounted partitions? i.e. if I have > a named pipe in a file system, > > # ls -ld /mysql/mysql.sock > srwxrwxrwx 1 mysql wheel 0 Feb 3 19:01 /mysql/mysql.sock > > # mysql --socket=/mysql/mysql.sock > Welcome to the MySQL monitor. Commands end with ; or \g. > Your MySQL connection id is 6 > Server version: 5.0.33-log FreeBSD port: mysql-server-5.0.33 > > Type 'help;' or '\h' for help. Type '\c' to clear the buffer. > > mysql> > > However if I make this available elsewhere via a null_fs mount: > > # mkdir /foo > # mount_nullfs /mysql /foo > # ls -ld /foo/mysql.sock > srwxrwxrwx 1 mysql wheel 0 Feb 3 19:01 /foo/mysql.sock > > # mysql --socket=/foo/mysql.sock -p > Enter password: > ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/foo/mysql.sock' (61) > > the socket stops working. > > However a hardlink to the socket works: > > # umount /foo > # ln /mysql/mysql.sock /foo/mysql.sock > > # mysql --socket=/foo/mysql.sock > Welcome to the MySQL monitor. Commands end with ; or \g. > Your MySQL connection id is 10 > Server version: 5.0.33-log FreeBSD port: mysql-server-5.0.33 > > Type 'help;' or '\h' for help. Type '\c' to clear the buffer. > > Is this a fundamental design issue with null_fs or a bug? > > There appears to be a lot of confusion on the lists about this point > as many people are trying to do this so as to make a single mysql > server available from within a number of jails, for instance. However > people appear to think that this is a limitation of the jail code, not a > limitation of the null_fs code. Having named pipes work in null_fs > filesystems would be a very handy thing indeed. > > I'd appreciate any insights into this. Just wanted to say that it seems like this should work, and I'm not yet certain why it doesn't. I've looked into it a bit, but my time is very limited, so I doubt I'll be able to put much more into it.. Eric From owner-freebsd-fs@FreeBSD.ORG Tue Feb 6 20:24:15 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C1C116A402; Tue, 6 Feb 2007 20:24:15 +0000 (UTC) (envelope-from flz@xbsd.org) Received: from postfix2-g20.free.fr (postfix2-g20.free.fr [212.27.60.43]) by mx1.freebsd.org (Postfix) with ESMTP id 3B22A13C48D; Tue, 6 Feb 2007 20:24:14 +0000 (UTC) (envelope-from flz@xbsd.org) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by postfix2-g20.free.fr (Postfix) with ESMTP id B83D0A2581D; Tue, 6 Feb 2007 20:00:48 +0100 (CET) Received: from smtp.xbsd.org (unknown [82.233.2.192]) by smtp1-g19.free.fr (Postfix) with ESMTP id 57CB89B8DD; Tue, 6 Feb 2007 21:00:36 +0100 (CET) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id 81CEF11AD8; Tue, 6 Feb 2007 21:00:32 +0100 (CET) X-Virus-Scanned: amavisd-new at xbsd.org Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id teLpK9H0kzYl; Tue, 6 Feb 2007 21:00:25 +0100 (CET) Received: from [193.120.13.130] (cream.xbsd.org [193.120.13.130]) by smtp.xbsd.org (Postfix) with ESMTP id 0281E1164F; Tue, 6 Feb 2007 21:00:24 +0100 (CET) Message-ID: <45C8DD5F.3000907@xbsd.org> Date: Tue, 06 Feb 2007 19:56:15 +0000 From: Florent Thoumie User-Agent: Thunderbird 1.5.0.9 (X11/20070122) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org, freebsd-fs@FreeBSD.org X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigEA21DBDE6DF7D3186E3D97BC" Cc: Subject: Use of kqueue/kevent NOTE_EXTEND fflag in VFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 20:24:15 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEA21DBDE6DF7D3186E3D97BC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'd like to use NOTE_EXTEND in the following cases: create, link, mkdir, mknod, rename, symlink for the parent vnode or the destination parent vnode (in the rename case). The rationale is that there's no way (or I don't see it) to know if a file/directory is removed or created when monitoring a directory. Using NOTE_EXTEND in the sense of "there's more files/directories" makes it possible to distinguish both cases. Another possibility could be to create new flags that would be the equivalent of IN_{CREATE,DELETE}_{FILE,SUBDIR}. Any thoughts? --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --------------enigEA21DBDE6DF7D3186E3D97BC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFyN1pMxEkbVFH3PQRCvOPAJ9YBjOshompn3KXspXFtxjxnTw03wCgh4Qa HrDEgaVrfdSvZau4hJZbF84= =4kxa -----END PGP SIGNATURE----- --------------enigEA21DBDE6DF7D3186E3D97BC-- From owner-freebsd-fs@FreeBSD.ORG Tue Feb 6 22:57:20 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A4A616A400 for ; Tue, 6 Feb 2007 22:57:19 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 9A6AE13C441 for ; Tue, 6 Feb 2007 22:57:18 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so25595uge for ; Tue, 06 Feb 2007 14:57:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=DXbkXn29lbL0vlvXcYBePG+oSDG9RYcugSIqcWX/HJcQ6WNWW3hFE4XVEvQoGLnbKwK9MQwD1aZcVeiHkMkCr0OIo0YfkzbczW8icMjRu9ZEo4M9fmILTz2BuqDQiN2K8EcEeUMWMxcjjcbydqOFw4A1YUG0NvlYX4pOJjd/wSA= Received: by 10.78.204.20 with SMTP id b20mr2006357hug.1170802633587; Tue, 06 Feb 2007 14:57:13 -0800 (PST) Received: by 10.48.162.13 with HTTP; Tue, 6 Feb 2007 14:57:13 -0800 (PST) Message-ID: <440b3e930702061457j7d254ad7j531b0258d45a51ab@mail.gmail.com> Date: Tue, 6 Feb 2007 17:57:13 -0500 From: "Ali Mashtizadeh" To: "Florent Thoumie" In-Reply-To: <45C8DD5F.3000907@xbsd.org> MIME-Version: 1.0 References: <45C8DD5F.3000907@xbsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Use of kqueue/kevent NOTE_EXTEND fflag in VFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 22:57:20 -0000 SSBzYXcgaW4gdGhlIHBhc3Qgc2V2ZXJhbCBwZW9wbGUgaGF2ZSBhc2tlZCBpZiB0aGVyZXMgYSB3 YXkgdG8gbW9uaXRvciBhbGwKZmlsZSBvcGVyYXRpb25zIChub3QgbGltaXRlZCB0byBhIHNldCBv ZiBWbm9kZXMpLiBJcyB0aGlzIGxpa2VseSB0byBiZQppbXBsZW1lbnRlZCBhbnkgdGltZSBzb29u PyBPciBpcyB0aGVyZSBhIGdvb2QgYWx0ZXJuYXRpdmU/CgpPbiAyLzYvMDcsIEZsb3JlbnQgVGhv dW1pZSA8Zmx6QHhic2Qub3JnPiB3cm90ZToKPgo+IEknZCBsaWtlIHRvIHVzZSBOT1RFX0VYVEVO RCBpbiB0aGUgZm9sbG93aW5nIGNhc2VzOiBjcmVhdGUsIGxpbmssIG1rZGlyLAo+IG1rbm9kLCBy ZW5hbWUsIHN5bWxpbmsgZm9yIHRoZSBwYXJlbnQgdm5vZGUgb3IgdGhlIGRlc3RpbmF0aW9uIHBh cmVudAo+IHZub2RlIChpbiB0aGUgcmVuYW1lIGNhc2UpLgo+Cj4gVGhlIHJhdGlvbmFsZSBpcyB0 aGF0IHRoZXJlJ3Mgbm8gd2F5IChvciBJIGRvbid0IHNlZSBpdCkgdG8ga25vdyBpZiBhCj4gZmls ZS9kaXJlY3RvcnkgaXMgcmVtb3ZlZCBvciBjcmVhdGVkIHdoZW4gbW9uaXRvcmluZyBhIGRpcmVj dG9yeS4gVXNpbmcKPiBOT1RFX0VYVEVORCBpbiB0aGUgc2Vuc2Ugb2YgInRoZXJlJ3MgbW9yZSBm aWxlcy9kaXJlY3RvcmllcyIgbWFrZXMgaXQKPiBwb3NzaWJsZSB0byBkaXN0aW5ndWlzaCBib3Ro IGNhc2VzLgo+Cj4gQW5vdGhlciBwb3NzaWJpbGl0eSBjb3VsZCBiZSB0byBjcmVhdGUgbmV3IGZs YWdzIHRoYXQgd291bGQgYmUgdGhlCj4gZXF1aXZhbGVudCBvZiBJTl97Q1JFQVRFLERFTEVURX1f e0ZJTEUsU1VCRElSfS4KPgo+IEFueSB0aG91Z2h0cz8KPgo+IC0tCj4gRmxvcmVudCBUaG91bWll Cj4gZmx6QEZyZWVCU0Qub3JnCj4gRnJlZUJTRCBDb21taXR0ZXIKPgo+Cj4KCgotLSAKQWxpIE1h c2h0aXphZGVoCti52YTbjCDZhdi02KrbjCDYstin2K/Zhwo= From owner-freebsd-fs@FreeBSD.ORG Wed Feb 7 10:05:28 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8434716A405 for ; Wed, 7 Feb 2007 10:05:26 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8C0F613C491 for ; Wed, 7 Feb 2007 10:05:22 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HEj86-0005bF-4C for freebsd-fs@freebsd.org; Wed, 07 Feb 2007 10:30:18 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Feb 2007 10:30:18 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Feb 2007 10:30:18 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Wed, 07 Feb 2007 10:30:10 +0100 Lines: 18 Message-ID: References: <45C8DD5F.3000907@xbsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.9 (X11/20070110) In-Reply-To: <45C8DD5F.3000907@xbsd.org> Sender: news Cc: freebsd-hackers@freebsd.org Subject: Re: Use of kqueue/kevent NOTE_EXTEND fflag in VFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 10:05:29 -0000 Florent Thoumie wrote: > I'd like to use NOTE_EXTEND in the following cases: create, link, mkdir, > mknod, rename, symlink for the parent vnode or the destination parent > vnode (in the rename case). > > The rationale is that there's no way (or I don't see it) to know if a > file/directory is removed or created when monitoring a directory. Using > NOTE_EXTEND in the sense of "there's more files/directories" makes it > possible to distinguish both cases. > > Another possibility could be to create new flags that would be the > equivalent of IN_{CREATE,DELETE}_{FILE,SUBDIR}. > > Any thoughts? I'd welcome it because I have several ideas that would benefit from such thing. Separate "notes" for CREATE/DELETE (issued on a directory vnode, right?) would be better than single "extend" note. From owner-freebsd-fs@FreeBSD.ORG Wed Feb 7 10:34:39 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89DC816A400; Wed, 7 Feb 2007 10:34:38 +0000 (UTC) (envelope-from flz@xbsd.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id 41FD713C461; Wed, 7 Feb 2007 10:34:38 +0000 (UTC) (envelope-from flz@xbsd.org) Received: from smtp.xbsd.org (unknown [82.233.2.192]) by smtp5-g19.free.fr (Postfix) with ESMTP id 497C527AC4; Wed, 7 Feb 2007 11:34:37 +0100 (CET) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id 8BE3211B4E; Wed, 7 Feb 2007 11:34:31 +0100 (CET) X-Virus-Scanned: amavisd-new at xbsd.org Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pQBEPU3tVvHM; Wed, 7 Feb 2007 11:34:25 +0100 (CET) Received: from [193.95.134.156] (mayday.esat.net [193.95.134.156]) by smtp.xbsd.org (Postfix) with ESMTP id 7C11711AD2; Wed, 7 Feb 2007 11:34:24 +0100 (CET) Message-ID: <45C9AB28.7000509@xbsd.org> Date: Wed, 07 Feb 2007 10:34:16 +0000 From: Florent Thoumie User-Agent: Thunderbird 1.5.0.9 (X11/20070122) MIME-Version: 1.0 To: Ali Mashtizadeh References: <45C8DD5F.3000907@xbsd.org> <440b3e930702061457j7d254ad7j531b0258d45a51ab@mail.gmail.com> In-Reply-To: <440b3e930702061457j7d254ad7j531b0258d45a51ab@mail.gmail.com> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigD484ED5E0569E1A7986E803C" Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Use of kqueue/kevent NOTE_EXTEND fflag in VFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 10:34:39 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD484ED5E0569E1A7986E803C Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Ali Mashtizadeh wrote: > I saw in the past several people have asked if theres a way to monitor = all > file operations (not limited to a set of Vnodes). Is this likely to be > implemented any time soon? Or is there a good alternative? If I understand correctly what you're looking for, then you want beagle or tracker. --=20 Florent Thoumie flz@FreeBSD.org FreeBSD Committer --------------enigD484ED5E0569E1A7986E803C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFyasuMxEkbVFH3PQRCtJGAJ4xCxHj/ad6Gc/yM8jBrKfPEwVF1wCeL4mr j70yrmkRi0hEohRAqKIhBqo= =8Lbw -----END PGP SIGNATURE----- --------------enigD484ED5E0569E1A7986E803C-- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 7 10:47:51 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C92D16A49E; Wed, 7 Feb 2007 10:47:51 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from mailhost.tao.org.uk (transwarp.tao.org.uk [87.74.4.34]) by mx1.freebsd.org (Postfix) with ESMTP id B4FBA13C4B2; Wed, 7 Feb 2007 10:47:50 +0000 (UTC) (envelope-from joe@tao.org.uk) Received: from genius.tao.org.uk (wireless58.dhcp.tao.org.uk [87.74.4.58]) by mailhost.tao.org.uk (Postfix) with ESMTP id 92C9C6174; Wed, 7 Feb 2007 10:47:49 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 1000) id DD08140A8; Wed, 7 Feb 2007 10:47:47 +0000 (GMT) Date: Wed, 7 Feb 2007 10:47:47 +0000 From: Josef Karthauser To: Eric Anderson Message-ID: <20070207104747.GB4431@genius.tao.org.uk> References: <20070204023711.GA3393@genius.tao.org.uk> <45C8A9B2.4090605@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R3G7APHDIzY6R/pk" Content-Disposition: inline In-Reply-To: <45C8A9B2.4090605@freebsd.org> User-Agent: Mutt/1.5.11 Cc: hackers@freebsd.org, fs@freebsd.org Subject: Re: nullfs and named pipes. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 10:47:51 -0000 --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 06, 2007 at 10:15:46AM -0600, Eric Anderson wrote: > > > >Is this a fundamental design issue with null_fs or a bug? > > > >There appears to be a lot of confusion on the lists about this point > >as many people are trying to do this so as to make a single mysql > >server available from within a number of jails, for instance. However > >people appear to think that this is a limitation of the jail code, not a > >limitation of the null_fs code. Having named pipes work in null_fs > >filesystems would be a very handy thing indeed. > > > >I'd appreciate any insights into this. >=20 > Just wanted to say that it seems like this should work, and I'm not yet= =20 > certain why it doesn't. I've looked into it a bit, but my time is very= =20 > limited, so I doubt I'll be able to put much more into it.. >=20 It's been brought to my attention that there's been a PR open about it since April 2003: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/51583. It's got a patch in it, but it's not complete. I'd really really appreciated it if someone with file system foo could take a look and comment. Thanks thanks, Joe --R3G7APHDIzY6R/pk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iEYEARECAAYFAkXJrlMACgkQXVIcjOaxUBacNgCfWw8EMNOAYjJd76v5nkj+TJeq KEYAoLHIvU6/GiIKmAGHLyHiqy8z+9d8 =IbNb -----END PGP SIGNATURE----- --R3G7APHDIzY6R/pk-- From owner-freebsd-fs@FreeBSD.ORG Thu Feb 8 22:52:49 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59FCB16A409 for ; Thu, 8 Feb 2007 22:52:49 +0000 (UTC) (envelope-from simokawa@freebsd.org) Received: from mail4.ecc.u-tokyo.ac.jp (mail4.ecc.u-tokyo.ac.jp [133.11.205.98]) by mx1.freebsd.org (Postfix) with ESMTP id 0923C13C4B4 for ; Thu, 8 Feb 2007 22:52:48 +0000 (UTC) (envelope-from simokawa@freebsd.org) Received: from mail1.ecc.u-tokyo.ac.jp (mail1.ecc.u-tokyo.ac.jp [133.11.50.203]) by mail4.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id E1CDC5B1DB0 for ; Fri, 9 Feb 2007 07:31:15 +0900 (JST) Received: from spam002.ecc.u-tokyo.ac.jp (spam002.ecc.u-tokyo.ac.jp [133.11.50.195]) by mail1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 3212710069 for ; Fri, 9 Feb 2007 07:31:15 +0900 (JST) Received: from tora.nunu.org (219.3.182.10 [219.3.182.10]) by spam002.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.94) with ESMTP id <87wt2sth84.wl%simokawa@FreeBSD.ORG> for ; Fri, 9 Feb 2007 07:30:35 +0900 Date: Fri, 09 Feb 2007 07:30:35 +0900 Message-ID: <87wt2sth84.wl%simokawa@FreeBSD.ORG> From: Hidetoshi Shimokawa To: Pawel Jakub Dawidek In-Reply-To: <20061116015908.GB63195@garage.freebsd.pl> References: <20061116015908.GB63195@garage.freebsd.pl> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-pc-freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 219.3.182.10 X-FROM-DOMAIN: freebsd.org X-FROM-EMAIL: simokawa@freebsd.org Cc: freebsd-fs@FreeBSD.org Subject: ZFS on amd64 (Re: ZFS patches for FreeBSD.) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2007 22:52:49 -0000 Hi Pawel, At Thu, 16 Nov 2006 02:59:08 +0100, Pawel Jakub Dawidek wrote: > > [1 ] > Hi. > > This is a first set of patches, which allows to use ZFS file system from > OpenSolaris on FreeBSD. > > To apply the patch you need to have recent FreeBSD source (be sure you > have rev. 1.284 of src/sys/kern/kern_synch.c). > > To try it out you need i386 machine (this is what I tested) and kernel > without WITNESS compiled in (there are probably some warnings still). > > Currently it can only be compiled as a kernel module. Thank you for porting of ZFS. I tried to run your code on FreeBSD/amd64 and it seems running very well. It survives several "make -j8 buildworld/kernel" with the obj tree in ZFS. Here is what I did, 1. copy files from //depot/user/pjd/zfs/... (without vop_vptofh related changes) 2. delete sys/contrib/opensolaris/uts/common/sys/acl.h 3. add sys/contrib/opensolaris/uts/common/rpc/types.h from opensolaris (for vaild declaration of mem_alloc/mem_free for kernel) 4. replace "i386" in sys/modules/zfs/Makefile with ${MACHINE}. 5. apply the following patch. 6. build /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG ==== //depot/user/pjd/zfs/cddl/lib/Makefile#1 - /home/p4/zfs/cddl/lib/Makefile ==== @@ -1,3 +1,5 @@ +.if !defined(COMPAT_32BIT) SUBDIR= libavl libnvpair libumem libuutil libzfs #libzpool +.endif .include ==== //depot/user/pjd/zfs/sys/contrib/opensolaris/uts/common/fs/zfs/arc.c#27 - /home/p4/zfs/sys/contrib/opensolaris/uts/common/fs/zfs/arc.c ==== @@ -388,7 +388,7 @@ * Hash table routines */ -#define HT_LOCK_PAD 64 +#define HT_LOCK_PAD roundup(sizeof(kmutex_t), 8) struct ht_lock { kmutex_t ht_lock; ==== //depot/user/pjd/zfs/sys/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c#67 - /home/p4/zfs/sys/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c ==== @@ -201,7 +201,7 @@ * data (cmd == _FIO_SEEK_DATA). "off" is an in/out parameter. */ static int -zfs_holey(vnode_t *vp, int cmd, offset_t *off) +zfs_holey(vnode_t *vp, u_long cmd, offset_t *off) { znode_t *zp = VTOZ(vp); uint64_t noff = (uint64_t)*off; /* new offset */ @@ -1932,7 +1932,7 @@ mutex_exit(&zp->z_lock); - dmu_object_size_from_db(zp->z_dbuf, &blksize, &vap->va_nblocks); + dmu_object_size_from_db(zp->z_dbuf, &blksize, (u_longlong_t *)&vap->va_nblocks); vap->va_blksize = blksize; if (zp->z_blksz == 0) { @@ -3116,7 +3116,7 @@ } */ *ap; { int cmd = ap->a_name; - int *valp = ap->a_retval; + long *valp = ap->a_retval; #if 0 vnode_t *vp = ap->a_vp; znode_t *zp, *xzp; @@ -3164,9 +3164,11 @@ *valp = 0; /* TODO */ return (0); +#if 0 case _PC_MIN_HOLE_SIZE: *valp = (int)SPA_MINBLOCKSIZE; return (0); +#endif default: return (vop_stdpathconf(ap)); From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 07:02:30 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3729416A400 for ; Fri, 9 Feb 2007 07:02:30 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: from web58613.mail.re3.yahoo.com (web58613.mail.re3.yahoo.com [68.142.236.211]) by mx1.freebsd.org (Postfix) with SMTP id E0BDF13C4B9 for ; Fri, 9 Feb 2007 07:02:29 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: (qmail 65649 invoked by uid 60001); 9 Feb 2007 06:35:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ybyKxd3IMduR3uTN1UeboradYza+4GHVb/3vtjH4HbE83/L7CpWQMcNCWrAHrVPINoi9At5MDxNw4ir2FE10yZGB76ZB3iiAsNxxFhEPD8LTAq26RVpCYwcJF+kj+hMJUzxT6huZxqvLkipiEmb7qoi9jC+1gCJeYE7wRlnJu84=; X-YMail-OSG: EZA9JN8VM1kr0gj6InHl9R7z83aqXOJozuN71OVVSVn08yvZWH8Ild5Y2Rn_h8wDIjXcM3OAqLTNSpM1XDvKVLkqeO9wMb8PYiJ._Kvq6.OAyzfuLHYkFQ-- Received: from [71.136.246.192] by web58613.mail.re3.yahoo.com via HTTP; Thu, 08 Feb 2007 22:35:48 PST Date: Thu, 8 Feb 2007 22:35:48 -0800 (PST) From: Arone Silimantia To: freebsd-fs@freebsd.org MIME-Version: 1.0 Message-ID: <646424.65334.qm@web58613.mail.re3.yahoo.com> X-Mailman-Approved-At: Fri, 09 Feb 2007 12:24:57 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 07:02:30 -0000 FreeBSD 6.2-RELEASE. Big 3ware sata raid with 16 disks. First two disks are a mirror to boot off of. I installed the system with sysinstall and created all the partitions on the boot mirror, etc., and just didn't even touch the 14-disk array that was also created. So then I spent hours researching bsdlabel and gpt and blah blah blah, and I just got fed up and: dd if=/dev/zero of=/dev/da1 bs=1k count=1 newfs -m 0 /dev/da1 mount /dev/da1 /mnt And that's that. But it seems too good to be true! Can someone please comment on this scheme and if there are some hidden dangers or lack of functionality that I will regret in the future ? Will it fsck just like any other UFS2 partition I run ? Can I run quotas and snapshots and everything else on it, just like normal ? Other than the fact that I can't boot this, is there _any downside whatsoever_ to newfs'ing raw disk like this ? --------------------------------- Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 13:12:46 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CCFD716A400 for ; Fri, 9 Feb 2007 13:12:46 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8E9EB13C4A6 for ; Fri, 9 Feb 2007 13:12:46 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HFVYG-0007LY-8O for freebsd-fs@freebsd.org; Fri, 09 Feb 2007 14:12:32 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Feb 2007 14:12:32 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Feb 2007 14:12:32 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Fri, 09 Feb 2007 14:12:07 +0100 Lines: 36 Message-ID: References: <646424.65334.qm@web58613.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.9 (X11/20070110) In-Reply-To: <646424.65334.qm@web58613.mail.re3.yahoo.com> Sender: news Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 13:12:46 -0000 Arone Silimantia wrote: > dd if=/dev/zero of=/dev/da1 bs=1k count=1 > newfs -m 0 /dev/da1 > mount /dev/da1 /mnt > > And that's that. But it seems too good to be true! Can someone please > comment on this scheme and if there are some hidden dangers or lack of > functionality that I will regret in the future ? No dangers at the system level - you can create your file system on any storage-like device, use it and mount it any way you want. Raw disks are a perfectly valid target. > Will it fsck just like any other UFS2 partition I run ? Can I run > quotas and snapshots and everything else on it, just like normal ? Yes. > Other than the fact that I can't boot this, is there _any downside > whatsoever_ to newfs'ing raw disk like this ? Only "collateral" problems because of the partition size: a regular (non-softupdates) fsck will take a LONG time to finish and eat a LOT of memory while it's doing its stuff. You'll need a lot of swap space (1GB per TB? someone had empirical numbers on this, I'm sure) if you think you'll need to fsck it entirely. Creating snapshots will also take a long time on it, and you probably want to search the lists for recommendations about creating snapshots in a second level directory in order not to block the root directory. Related to this is background-fsck which works by creating snapshots, so you'll probably want to disable it. In any case, try every feature you think you'll need before deploying it. Also, write about your experience on this list :) From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 13:20:37 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07A3816A400 for ; Fri, 9 Feb 2007 13:20:37 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id BCF2913C461 for ; Fri, 9 Feb 2007 13:20:36 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1HFVfY-0000mp-PU for freebsd-fs@freebsd.org; Fri, 09 Feb 2007 14:20:04 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Feb 2007 14:20:04 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Feb 2007 14:20:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Fri, 09 Feb 2007 14:15:10 +0100 Lines: 5 Message-ID: References: <646424.65334.qm@web58613.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.9 (X11/20070110) In-Reply-To: Sender: news Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 13:20:37 -0000 Ivan Voras wrote: > Only "collateral" problems because of the partition size: a regular ^^^^^^^^^^^^^^ Sorry, "file system size". From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 13:34:20 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9693916A401 for ; Fri, 9 Feb 2007 13:34:20 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from smtp.voda.cz (gw.voda.cz [212.24.154.90]) by mx1.freebsd.org (Postfix) with ESMTP id 25F8913C4A5 for ; Fri, 9 Feb 2007 13:34:20 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from localhost (localhost [127.0.0.1]) by smtp.voda.cz (Postfix) with ESMTP id 5EB6E43C0D; Fri, 9 Feb 2007 14:34:18 +0100 (CET) Received: from smtp.voda.cz ([127.0.0.1]) by localhost (mail.voda.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08737-05; Fri, 9 Feb 2007 14:34:13 +0100 (CET) Received: from spyro.eiecon.net (unknown [213.151.77.190]) by smtp.voda.cz (Postfix) with ESMTP id DD20943C1E; Fri, 9 Feb 2007 14:34:12 +0100 (CET) Date: Fri, 09 Feb 2007 14:34:13 +0100 To: "Ivan Voras" , freebsd-fs@freebsd.org From: Indigo Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-2 MIME-Version: 1.0 References: <646424.65334.qm@web58613.mail.re3.yahoo.com> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: User-Agent: Opera Mail/9.10 (Win32) X-Virus-Scanned: by amavisd-new at voda.cz Cc: Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 13:34:20 -0000 Hi, does that mean that slicing and partitioning additional drives has no = advantages on a purely FreeBSD machine? Vasek On Fri, 09 Feb 2007 14:12:07 +0100, Ivan Voras wrote: > Arone Silimantia wrote: > >> dd if=3D/dev/zero of=3D/dev/da1 bs=3D1k count=3D1 >> newfs -m 0 /dev/da1 >> mount /dev/da1 /mnt >> >> And that's that. But it seems too good to be true! Can someone plea= se >> comment on this scheme and if there are some hidden dangers or lack o= f >> functionality that I will regret in the future ? > > No dangers at the system level - you can create your file system on an= y > storage-like device, use it and mount it any way you want. Raw disks a= re > a perfectly valid target. > >> Will it fsck just like any other UFS2 partition I run ? Can I run >> quotas and snapshots and everything else on it, just like normal ? > > Yes. > >> Other than the fact that I can't boot this, is there _any downside >> whatsoever_ to newfs'ing raw disk like this ? > > Only "collateral" problems because of the partition size: a regular > (non-softupdates) fsck will take a LONG time to finish and eat a LOT o= f > memory while it's doing its stuff. You'll need a lot of swap space (1G= B > per TB? someone had empirical numbers on this, I'm sure) if you think > you'll need to fsck it entirely. Creating snapshots will also take a > long time on it, and you probably want to search the lists for > recommendations about creating snapshots in a second level directory i= n > order not to block the root directory. Related to this is > background-fsck which works by creating snapshots, so you'll probably > want to disable it. > > In any case, try every feature you think you'll need before deploying = it. > > Also, write about your experience on this list :) > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 13:38:23 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8635F16A401 for ; Fri, 9 Feb 2007 13:38:23 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 52D3713C48D for ; Fri, 9 Feb 2007 13:38:21 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l19Dc7kV003166; Fri, 9 Feb 2007 07:38:07 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45CC793F.7090003@freebsd.org> Date: Fri, 09 Feb 2007 07:38:07 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Ivan Voras References: <646424.65334.qm@web58613.mail.re3.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2544/Fri Feb 9 02:44:48 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 13:38:23 -0000 On 02/09/07 07:12, Ivan Voras wrote: > Arone Silimantia wrote: > >> dd if=/dev/zero of=/dev/da1 bs=1k count=1 >> newfs -m 0 /dev/da1 >> mount /dev/da1 /mnt >> >> And that's that. But it seems too good to be true! Can someone please >> comment on this scheme and if there are some hidden dangers or lack of >> functionality that I will regret in the future ? > > No dangers at the system level - you can create your file system on any > storage-like device, use it and mount it any way you want. Raw disks are > a perfectly valid target. As a side benefit, one might also get a performance *increase* because not having a slice/partition in the way might make the file system blocks line up better with the stripe size. Scott Long has posted about this in the past, either here, or on -performance, or somewhere. I can't find the thread right off, but it's out there (he wrote a very good description of what happens, why, etc). FWIW, I almost always do it this way. >> Will it fsck just like any other UFS2 partition I run ? Can I run >> quotas and snapshots and everything else on it, just like normal ? > > Yes. > >> Other than the fact that I can't boot this, is there _any downside >> whatsoever_ to newfs'ing raw disk like this ? > > Only "collateral" problems because of the partition size: a regular > (non-softupdates) fsck will take a LONG time to finish and eat a LOT of > memory while it's doing its stuff. You'll need a lot of swap space (1GB > per TB? someone had empirical numbers on this, I'm sure) if you think > you'll need to fsck it entirely. Creating snapshots will also take a > long time on it, and you probably want to search the lists for > recommendations about creating snapshots in a second level directory in > order not to block the root directory. Related to this is > background-fsck which works by creating snapshots, so you'll probably > want to disable it. I have 5 10Tb file systems (and some 2Tb ones, but who cares about those tiny things? :)), and I can tell you that an empty huge file system is pretty easily fsck-able, but a full one will kill you. It greatly depends on how many files (inodes) you have used on the file system. If you have a massive amount of small files, you'll be eating up a ton of memory. My 'rule of thumb' for my data (which averages to about 16k/file) is 1G of memory for each 1Tb of disk space used. So, on a 10Tb file system, if I ever want the fsck to complete, I need an AMD64 box with *at least* 10G of memory, plus a lot of time. A *lot* of time. By 'a lot', I mean anywhere from a day, to several days. > In any case, try every feature you think you'll need before deploying it. > > Also, write about your experience on this list :) I second that. It's important to share anything we can, so we see what others are doing, what the needs are, etc. I also recommend looking at gjournal, now in -CURRENT. I'm not sure if it's still considered beta, but care should be taken when using it of course. However, I use it for many tens of TB of data, and I'm a happy gjournal fan (thanks Pawel!). Eric From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 13:55:19 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45DEC16A400 for ; Fri, 9 Feb 2007 13:55:19 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 068EF13C48E for ; Fri, 9 Feb 2007 13:55:18 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HFW6v-0007rn-7T for freebsd-fs@freebsd.org; Fri, 09 Feb 2007 14:48:21 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Feb 2007 14:48:21 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Feb 2007 14:48:21 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Fri, 09 Feb 2007 14:44:23 +0100 Lines: 13 Message-ID: References: <646424.65334.qm@web58613.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.9 (X11/20070110) In-Reply-To: Sender: news Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 13:55:19 -0000 Indigo wrote: > Hi, > does that mean that slicing and partitioning additional drives has no > advantages on a purely FreeBSD machine? No, except organizational - you might want to use different file systems or different file system parameters on each partition/slice, you might want to distribute data so that if one file system gets full (for example, with logs) the others are not affected, etc. There was a pretty long list of organizational benefits of partitioning on the questions- mailing list recently. But from a system point of view, no - partitioning is not required. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 14:04:34 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CE35516A76C for ; Fri, 9 Feb 2007 14:04:34 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from smtp.voda.cz (gw.voda.cz [212.24.154.90]) by mx1.freebsd.org (Postfix) with ESMTP id 8BD0713C491 for ; Fri, 9 Feb 2007 14:04:34 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from localhost (localhost [127.0.0.1]) by smtp.voda.cz (Postfix) with ESMTP id 4889843C02 for ; Fri, 9 Feb 2007 15:04:33 +0100 (CET) Received: from smtp.voda.cz ([127.0.0.1]) by localhost (mail.voda.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27649-08 for ; Fri, 9 Feb 2007 15:04:30 +0100 (CET) Received: from spyro.eiecon.net (unknown [213.151.77.190]) by smtp.voda.cz (Postfix) with ESMTP id 20F0C4381F for ; Fri, 9 Feb 2007 15:04:29 +0100 (CET) Date: Fri, 09 Feb 2007 15:04:30 +0100 To: freebsd-fs@freebsd.org From: Indigo Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-2 MIME-Version: 1.0 References: <646424.65334.qm@web58613.mail.re3.yahoo.com> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: User-Agent: Opera Mail/9.10 (Win32) X-Virus-Scanned: by amavisd-new at voda.cz Subject: Expanding drives X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 14:04:34 -0000 Hello everyone, my new RAID card just arrived in the mail and it can expand an array. My question is - how can I expand a filesystem(slice&parititon OR raw device) when I add another drive to a RAID-5 for example. I will probably flood this mailing list with questions today because theres a lot of things I couldn;t find in the handbook. Vasek From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 14:14:17 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07BDF16A400 for ; Fri, 9 Feb 2007 14:14:17 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id CFA6713C461 for ; Fri, 9 Feb 2007 14:14:16 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l19EEB9I009889; Fri, 9 Feb 2007 08:14:12 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45CC81B4.2050501@freebsd.org> Date: Fri, 09 Feb 2007 08:14:12 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Indigo References: <646424.65334.qm@web58613.mail.re3.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2544/Fri Feb 9 02:44:48 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: Expanding drives X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 14:14:17 -0000 On 02/09/07 08:04, Indigo wrote: > Hello everyone, > my new RAID card just arrived in the mail and it can expand an array. > > My question is - how can I expand a filesystem(slice&parititon OR raw > device) when I add another drive to a RAID-5 for example. > > I will probably flood this mailing list with questions today because > theres a lot of things I couldn;t find in the handbook. See growfs(8) Eric From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 14:29:55 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B29F16A401 for ; Fri, 9 Feb 2007 14:29:55 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from smtp.voda.cz (gw.voda.cz [212.24.154.90]) by mx1.freebsd.org (Postfix) with ESMTP id 19E5E13C481 for ; Fri, 9 Feb 2007 14:29:55 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from localhost (localhost [127.0.0.1]) by smtp.voda.cz (Postfix) with ESMTP id 0D3B843C5D for ; Fri, 9 Feb 2007 15:29:53 +0100 (CET) Received: from smtp.voda.cz ([127.0.0.1]) by localhost (mail.voda.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16969-06 for ; Fri, 9 Feb 2007 15:29:51 +0100 (CET) Received: from spyro.eiecon.net (unknown [213.151.77.190]) by smtp.voda.cz (Postfix) with ESMTP id C61CE43C37 for ; Fri, 9 Feb 2007 15:29:50 +0100 (CET) Date: Fri, 09 Feb 2007 15:29:50 +0100 To: "freebsd-fs@freebsd.org" From: Indigo Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-2 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Message-ID: User-Agent: Opera Mail/9.10 (Win32) X-Virus-Scanned: by amavisd-new at voda.cz Subject: labels and layout X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 14:29:55 -0000 Hello everyone, heres a batch of question: Im looking for a way to mount disks by label instead of device. Im on 6.2 and I can't use ZFS until it gets released. I saw that tunefs and newfs have some label option - but I assumed it's not the kind of label I want because no one is using it. An example with AdvFS (Tru64): # mount root_domain#root on / type advfs (rw) /proc on /proc type procfs (rw) usr_domain#usr on /usr type advfs (rw) var_domain#var on /var type advfs (rw) I just think it's stupid to edit fstab every time Im swapping things inside the box - I think it's needless. Second thing I was wondering about is: Did anyone ever try to break down the performance requirements of various system directories? Basically - which directories benefit from faster seeks or higher read/write speeds. I know this highly depends on actual services and that I should put the machine together and watch its needs before finalizing disk-layout - but it would take a lot of time and Im looking for any advice that can save me time. Thanks, Vasek From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 15:07:35 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 924D116A400 for ; Fri, 9 Feb 2007 15:07:35 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (grnl-static-02-0046.dsl.iowatelecom.net [69.66.56.110]) by mx1.freebsd.org (Postfix) with ESMTP id 5575613C491 for ; Fri, 9 Feb 2007 15:07:35 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l19F7YUa008590; Fri, 9 Feb 2007 09:07:34 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l19F7YWB008589; Fri, 9 Feb 2007 09:07:34 -0600 (CST) (envelope-from brooks) Date: Fri, 9 Feb 2007 09:07:34 -0600 From: Brooks Davis To: Indigo Message-ID: <20070209150734.GB1193@lor.one-eyed-alien.net> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="V0207lvV8h4k8FAm" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Fri, 09 Feb 2007 09:07:34 -0600 (CST) Cc: "freebsd-fs@freebsd.org" Subject: Re: labels and layout X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 15:07:35 -0000 --V0207lvV8h4k8FAm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 09, 2007 at 03:29:50PM +0100, Indigo wrote: > Hello everyone, > heres a batch of question: >=20 > Im looking for a way to mount disks by label instead of device. Im on 6.2= =20 > and I can't use ZFS until it gets released. > I saw that tunefs and newfs have some label option - but I assumed it's = =20 > not the kind of label I want because no one is using it. >=20 > An example with AdvFS (Tru64): > # mount > root_domain#root on / type advfs (rw) > /proc on /proc type procfs (rw) > usr_domain#usr on /usr type advfs (rw) > var_domain#var on /var type advfs (rw) >=20 > I just think it's stupid to edit fstab every time Im swapping things =20 > inside the box - I think it's needless. ufs labels as set by tunefs and newfs work fine as long as your load the geom_label module. I'm honestly not sure what it isn't in GENERIC. It's really useful. You can also use glabel labels for your swap partitions. -- Brooks --V0207lvV8h4k8FAm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFzI41XY6L6fI4GtQRApgIAJ4qz7BKvHNblNZQ7emu2kiwkey2nACfV2fR doQV2nGOKZzkYmLLVNgh7QM= =OZ6i -----END PGP SIGNATURE----- --V0207lvV8h4k8FAm-- From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 15:28:24 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D32C216A402 for ; Fri, 9 Feb 2007 15:28:24 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id A3AD313C4A8 for ; Fri, 9 Feb 2007 15:28:24 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l19FSLBR023704; Fri, 9 Feb 2007 09:28:21 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45CC9315.6050500@freebsd.org> Date: Fri, 09 Feb 2007 09:28:21 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Brooks Davis References: <20070209150734.GB1193@lor.one-eyed-alien.net> In-Reply-To: <20070209150734.GB1193@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2544/Fri Feb 9 02:44:48 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: "freebsd-fs@freebsd.org" Subject: Re: labels and layout X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 15:28:24 -0000 On 02/09/07 09:07, Brooks Davis wrote: > On Fri, Feb 09, 2007 at 03:29:50PM +0100, Indigo wrote: >> Hello everyone, >> heres a batch of question: >> >> Im looking for a way to mount disks by label instead of device. Im on 6.2 >> and I can't use ZFS until it gets released. >> I saw that tunefs and newfs have some label option - but I assumed it's >> not the kind of label I want because no one is using it. >> >> An example with AdvFS (Tru64): >> # mount >> root_domain#root on / type advfs (rw) >> /proc on /proc type procfs (rw) >> usr_domain#usr on /usr type advfs (rw) >> var_domain#var on /var type advfs (rw) >> >> I just think it's stupid to edit fstab every time Im swapping things >> inside the box - I think it's needless. > > ufs labels as set by tunefs and newfs work fine as long as your load the > geom_label module. I'm honestly not sure what it isn't in GENERIC. > It's really useful. You can also use glabel labels for your swap > partitions. I agree! I use it heavily, pretty much on every system I touch. I label swap, root, etc. Who should we nag^H^H^Hask about including it in GENERIC? Eric From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 16:40:52 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D17F16A403; Fri, 9 Feb 2007 16:40:52 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (grnl-static-02-0046.dsl.iowatelecom.net [69.66.56.110]) by mx1.freebsd.org (Postfix) with ESMTP id B51C013C494; Fri, 9 Feb 2007 16:40:51 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l19GeosQ009431; Fri, 9 Feb 2007 10:40:51 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l19GeoX4009430; Fri, 9 Feb 2007 10:40:50 -0600 (CST) (envelope-from brooks) Date: Fri, 9 Feb 2007 10:40:50 -0600 From: Brooks Davis To: Eric Anderson Message-ID: <20070209164050.GA9016@lor.one-eyed-alien.net> References: <20070209150734.GB1193@lor.one-eyed-alien.net> <45CC9315.6050500@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline In-Reply-To: <45CC9315.6050500@freebsd.org> User-Agent: Mutt/1.5.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Fri, 09 Feb 2007 10:40:51 -0600 (CST) Cc: "freebsd-fs@freebsd.org" , Brooks Davis Subject: Re: labels and layout X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 16:40:52 -0000 --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 09, 2007 at 09:28:21AM -0600, Eric Anderson wrote: > On 02/09/07 09:07, Brooks Davis wrote: > >On Fri, Feb 09, 2007 at 03:29:50PM +0100, Indigo wrote: > >>Hello everyone, > >> heres a batch of question: > >> > >>Im looking for a way to mount disks by label instead of device. Im on 6= =2E2=20 > >>and I can't use ZFS until it gets released. > >>I saw that tunefs and newfs have some label option - but I assumed it's= =20 > >>not the kind of label I want because no one is using it. > >> > >>An example with AdvFS (Tru64): > >># mount > >>root_domain#root on / type advfs (rw) > >>/proc on /proc type procfs (rw) > >>usr_domain#usr on /usr type advfs (rw) > >>var_domain#var on /var type advfs (rw) > >> > >>I just think it's stupid to edit fstab every time Im swapping things = =20 > >>inside the box - I think it's needless. > > > >ufs labels as set by tunefs and newfs work fine as long as your load the > >geom_label module. I'm honestly not sure what it isn't in GENERIC. > >It's really useful. You can also use glabel labels for your swap > >partitions. >=20 > I agree! I use it heavily, pretty much on every system I touch. I=20 > label swap, root, etc. Who should we nag^H^H^Hask about including it in= =20 > GENERIC? I checked with Pawel and will commit it shortly. -- Brooks --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFzKQSXY6L6fI4GtQRAmalAJ4zOzgMsMzEx8ZCwACtezK4PkNBTQCg3Hl2 6RqQ4DKjJGmwwNEssRVAalw= =9iOR -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY-- From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 17:01:53 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 036DE16A403 for ; Fri, 9 Feb 2007 17:01:53 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 6487013C49D for ; Fri, 9 Feb 2007 17:01:52 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tcfqps@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l19H1feU054222; Fri, 9 Feb 2007 18:01:46 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l19H1fCH054221; Fri, 9 Feb 2007 18:01:41 +0100 (CET) (envelope-from olli) Date: Fri, 9 Feb 2007 18:01:41 +0100 (CET) Message-Id: <200702091701.l19H1fCH054221@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG, aronesimi@yahoo.com In-Reply-To: <646424.65334.qm@web58613.mail.re3.yahoo.com> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 09 Feb 2007 18:01:47 +0100 (CET) Cc: Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG, aronesimi@yahoo.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 17:01:53 -0000 Arone Silimantia wrote: > Big 3ware sata raid with 16 disks. First two disks are a mirror to > boot off of. I installed the system with sysinstall and created all the > partitions on the boot mirror, etc., and just didn't even touch the > 14-disk array that was also created. > [...] > newfs -m 0 /dev/da1 You didn't mention the size of the FS, but I guess it's at least 4 TB, probably more. You'll probably want to reduce the inode density (i.e. increase the bytes-per-inode ratio). With the default value, an fsck will be a royal pain, no matter whether you use background fsck (with snapshots) or not. It might even not work at all if you don't have a huge amount of RAM. If you increase the ratio to 64 K, it will lower the fsck time and RAM requirement by an order of magnitude, while there are still about 15 million inodes available per TB. If possible, increase the ratio (-i option) further. It depends on the expected average file size and the maximum number of files that you intend to store on the FS, of course. Depending on your application, it might also make sense to _carefully_ (!) adjust the fragment and block sizes of the FS (-f and -b options to newfs). However, note that non- standard values are not widely used and might expose bugs, especially on large file systems. If you change them, you should at least perform some extensive stress testing. Another thing that should be mentioned is the fact that "-m 0" will result in two things: First, it will make the FS slower, especially when its getting full, then it will be _much_ slower. Second, it increases fragmentation. I recommend you don't use the -m option at leave it at the default. Yes, that means that a whole lot of GB will not be available to users (non-root), but for that price you'll get a fast file system. Also note that you can change that option at a later date with tunefs(8), so if you decide that you _really_ need that extra space, and speed is not an issue at all, then you can change the -m value any time. Just my two cents. Oh by the way, I also agree with Eric that you should have a look at gjournal. It pratically removes the fsck issues. At the moment it's only in -current, but I think Pawel provided a port for 6.x. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 17:19:45 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6AF4016A400 for ; Fri, 9 Feb 2007 17:19:45 +0000 (UTC) (envelope-from redchin@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id F225F13C4B2 for ; Fri, 9 Feb 2007 17:19:42 +0000 (UTC) (envelope-from redchin@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1163484nfc for ; Fri, 09 Feb 2007 09:19:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=K8V3al18uMzduJyc8KFKRfJzJaVn0ThYW0nz9K0dNLA0epLnRhRk0AfiQJ2jBHnaEB6z5rdgq3gkd8C4/+R/RTbYmgM/+JMtzlCJfAP6cojgd35sEVD9UfEjTNrKLlRjzRiCK8CeGN63DF+/ktr0R2lmcXhQAZ8oT68dixAhbEE= Received: by 10.82.175.2 with SMTP id x2mr4872329bue.1171040835991; Fri, 09 Feb 2007 09:07:15 -0800 (PST) Received: by 10.82.119.10 with HTTP; Fri, 9 Feb 2007 09:07:15 -0800 (PST) Message-ID: <1d3ed48c0702090907j368d76c0y820424e9a3609288@mail.gmail.com> Date: Fri, 9 Feb 2007 09:07:15 -0800 From: "Kevin Downey" To: Indigo In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: "freebsd-fs@freebsd.org" Subject: Re: labels and layout X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 17:19:45 -0000 On 2/9/07, Indigo wrote: > Hello everyone, > heres a batch of question: > > Im looking for a way to mount disks by label instead of device. Im on 6.2 > and I can't use ZFS until it gets released. > I saw that tunefs and newfs have some label option - but I assumed it's > not the kind of label I want because no one is using it. > > An example with AdvFS (Tru64): > # mount > root_domain#root on / type advfs (rw) > /proc on /proc type procfs (rw) > usr_domain#usr on /usr type advfs (rw) > var_domain#var on /var type advfs (rw) > > I just think it's stupid to edit fstab every time Im swapping things > inside the box - I think it's needless. > > > geom_lable.ko is I think the kernel module for glabel. Works great. The labels on filesystems show up in /dev/label, kpd@zifnab ~% ls /dev/label BigDisk.root BigDisk.swap BigDisk.usr BigDisk.var -- The biggest problem with communication is the illusion that it has occurred. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 19:06:53 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B7B816A608 for ; Fri, 9 Feb 2007 19:06:53 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: from web58610.mail.re3.yahoo.com (web58610.mail.re3.yahoo.com [68.142.236.208]) by mx1.freebsd.org (Postfix) with SMTP id 0C46A13C46B for ; Fri, 9 Feb 2007 19:06:52 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: (qmail 15608 invoked by uid 60001); 9 Feb 2007 19:06:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ARkfD/0w42Nkb54Em2NEN53Qz6HgmF4y5TN5lHVQWh7+18nXIASWx59rp/POrm/O2Dv/f49/Iaz//JEzNfV0bfTfd4hFX9hP0hJV3+fC/RkA78bsGhjERfnTNgar5SUhLiQAlXDfqOHh5U5W4Z3/l/YNwTziy87GnvZF/s5Q3oU=; X-YMail-OSG: TSUDDHIVM1nXLfeYMobxoADAZ.8RlqB4rjFj1A3b Received: from [71.136.246.192] by web58610.mail.re3.yahoo.com via HTTP; Fri, 09 Feb 2007 11:06:52 PST Date: Fri, 9 Feb 2007 11:06:52 -0800 (PST) From: Arone Silimantia To: freebsd-fs@FreeBSD.ORG In-Reply-To: <200702091701.l19H1fCH054221@lurza.secnetix.de> MIME-Version: 1.0 Message-ID: <506226.11053.qm@web58610.mail.re3.yahoo.com> X-Mailman-Approved-At: Fri, 09 Feb 2007 21:17:39 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 19:06:53 -0000 Oliver, Thank you for your detailed response - my own response is inline below: Oliver Fromme wrote: Arone Silimantia wrote: > Big 3ware sata raid with 16 disks. First two disks are a mirror to > boot off of. I installed the system with sysinstall and created all the > partitions on the boot mirror, etc., and just didn't even touch the > 14-disk array that was also created. > [...] > newfs -m 0 /dev/da1 You didn't mention the size of the FS, but I guess it's at least 4 TB, probably more. Well, in the subject line I mentioned 7 TB, but I have since rearranged some things and it will be 5.5 TB. You'll probably want to reduce the inode density (i.e. increase the bytes-per-inode ratio). With the default value, an fsck will be a royal pain, no matter whether you use background fsck (with snapshots) or not. It might even not work at all if you don't have a huge amount of RAM. Well, I have 4 GB of physical RAM, and 4 GB of swap - so does that total of 8 GB satisfy the "1 GB per TB" requirement, or do I really need >5.5 GB of actual swap space (in addition to the physical) ? If you increase the ratio to 64 K, it will lower the fsck time and RAM requirement by an order of magnitude, while there are still about 15 million inodes available per TB. If possible, increase the ratio (-i option) further. It depends on the expected average file size and the maximum number of files that you intend to store on the FS, of course. Ok, I will look into this. My data population uses a little less than 5 million inodes per TB, so this may be workable to tune. So I see the default is '4' - so I could run newfs with: newfs -i 8 to do what you are suggesting ? Depending on your application, it might also make sense to _carefully_ (!) adjust the fragment and block sizes of the FS (-f and -b options to newfs). However, note that non- standard values are not widely used and might expose bugs, especially on large file systems. If you change them, you should at least perform some extensive stress testing. I think I'll make things simple by steering clear of this... Another thing that should be mentioned is the fact that "-m 0" will result in two things: First, it will make the FS slower, especially when its getting full, then it will be _much_ slower. Second, it increases fragmentation. I recommend you don't use the -m option at leave it at the default. Yes, that means that a whole lot of GB will not be available to users (non-root), but for that price you'll get a fast file system. Also note that you can change that option at a later date with tunefs(8), so if you decide that you _really_ need that extra space, and speed is not an issue at all, then you can change the -m value any time. Ok, that' s good advice - I will leave it at the default. Oh by the way, I also agree with Eric that you should have a look at gjournal. It pratically removes the fsck issues. At the moment it's only in -current, but I think Pawel provided a port for 6.x. Well, I don't mind a 24 hour fsck, and I would like to remove complexity and not be so on the bleeding edge with things. Since I am only using 5mil inodes per TB anyway, that ends up being 25-30 million inodes in the 5 TB drive which I think could fsck in a day or so. I just need to know if my 4+4 GB of memory is enough, and if this option in loader.conf: kern.maxdsiz="2048000000" is sufficient... Again, many thanks. --------------------------------- Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 21:35:38 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8536216A403 for ; Fri, 9 Feb 2007 21:35:38 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.230]) by mx1.freebsd.org (Postfix) with ESMTP id 4750C13C4AC for ; Fri, 9 Feb 2007 21:35:38 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: by wr-out-0506.google.com with SMTP id i22so1019664wra for ; Fri, 09 Feb 2007 13:35:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=NWXu6EtP4BFbtQcfNm056MFNKs+ezfqGTrQdk8TNWpfoQt799U4zcqi98+PfnyAh4PB3U+sl8vrJQhYpUteY717DcTB6mF3swp2lvAKGUHL3S3H75vp7WgQFESj8aSwUO79u8u6is+etVTkuvh1cs4PE+Y4FLEz1HlwQ2Ec41iw= Received: by 10.114.152.17 with SMTP id z17mr6393213wad.1171056935875; Fri, 09 Feb 2007 13:35:35 -0800 (PST) Received: by 10.114.175.5 with HTTP; Fri, 9 Feb 2007 13:35:35 -0800 (PST) Message-ID: Date: Fri, 9 Feb 2007 19:35:35 -0200 From: "Victor Loureiro Lima" To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: /usr/bin/du + crontab weird bug X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 21:35:38 -0000 Hello -hackers and -fs, Sorry for the cross-post but I didnt know where this particular post belonged to... In a .br FreeBSD related mailing-list a user seems to have a found a bug when using /usr/bin/du and crontab together, I am posting it here to see what responses we get: root@zion# du -s /etc 2544 /etc root@zion# cat /etc/crontab | grep du 30 19 * * 5 root /usr/bin/du -s /etc >> /tmp/lele root@zion# date Fri Feb 9 19:29:30 BRST 2007 root@zion# cat /tmp/lele 5088 /etc root@zion# du -s /etc 2544 /etc What gives that when "/usr/bin/du -s" is running from crontab is gives the exact double of entries in the directory but when it is running from console itself, it doesnt display the same amount of entries!?!?!?! Weird bug... /usr/bin/du version is: $FreeBSD: src/usr.bin/du/du.c,v 1.38.2.1 2006/06/04 10:23:08 maxim Exp$ uname -a is: FreeBSD zion 6.2-RELEASE FreeBSD 6.2-RELEASE #19: Thu Feb 8 11:00:59 BRST 2007 setuid@zion:/usr/obj/usr/src/sys/zion.kernel amd64 ciao, victor loureiro lima From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 21:56:23 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECB0F16A400 for ; Fri, 9 Feb 2007 21:56:23 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30309.mail.mud.yahoo.com (web30309.mail.mud.yahoo.com [209.191.69.71]) by mx1.freebsd.org (Postfix) with SMTP id 9DD0113C48D for ; Fri, 9 Feb 2007 21:56:23 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 94792 invoked by uid 60001); 9 Feb 2007 21:56:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=CBDOX2e2uMvmz4QiaJZeTJTll92HrmP9TTX+VNX/fhwqe5Cfv/xDi6oAw91eLKxHV5KoX3ifjj7/fVZnpsCAjn7L/uWuIIwwZej//mdYaRGeXB8WVFd2xqtecB55Ap6mDnUb/i8EDPR9GcVR3en5B6AKqJ1rIw5Cr3EjAkku/5g=; X-YMail-OSG: 2Xyz54EVM1kTXyj9CZSPZJWPD_YbBt_YPogj4Fr7ukpAOaw8od0x49xMMuJrjiFhBH.kOYQ23N77Vf55DF2vs.gO.J6bjOGAAF32zg.qkPZTFNNc8xZhcoKFyAA00z49UivdOXZEcwUK_JI- Received: from [213.54.162.179] by web30309.mail.mud.yahoo.com via HTTP; Fri, 09 Feb 2007 13:56:22 PST Date: Fri, 9 Feb 2007 13:56:22 -0800 (PST) From: "R. B. Riddick" To: Victor Loureiro Lima , freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <205542.91900.qm@web30309.mail.mud.yahoo.com> Cc: Subject: Re: /usr/bin/du + crontab weird bug X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 21:56:24 -0000 --- Victor Loureiro Lima wrote: > root@zion# du -s /etc > 2544 /etc > > What gives that when "/usr/bin/du -s" is running from crontab is gives > the exact double of entries in the directory but when it is running > from console itself, it doesnt display the same amount of > entries!?!?!?! > I think, it is about block size: in the crontab environment block size is 512B and in ur shell it is 1024B. There is an environment variable: BLOCKSIZE and there is an option: -k Just try "du -ks /etc" in ur crontab... -Arne ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 22:06:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D5C4716A402 for ; Fri, 9 Feb 2007 22:06:41 +0000 (UTC) (envelope-from mwm-dated-1171921255.ffef4d@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 6220613C46B for ; Fri, 9 Feb 2007 22:06:41 +0000 (UTC) (envelope-from mwm-dated-1171921255.ffef4d@mired.org) Received: (qmail 10544 invoked by uid 1001); 9 Feb 2007 21:40:55 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Fri, 09 Feb 2007 16:40:55 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17868.60007.226858.275351@bhuda.mired.org> Date: Fri, 9 Feb 2007 16:40:55 -0500 To: "Victor Loureiro Lima" In-Reply-To: References: X-Mailer: VM 7.17 under 21.4 (patch 20) "Double Solitaire" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: /usr/bin/du + crontab weird bug X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 22:06:41 -0000 In , Victor Loureiro Lima typed: > Hello -hackers and -fs, > > Sorry for the cross-post but I didnt know where this particular post > belonged to... > In a .br FreeBSD related mailing-list a user seems to have a found a > bug when using /usr/bin/du and crontab together, I am posting it here > to see what responses we get: > > root@zion# du -s /etc > 2544 /etc > root@zion# cat /etc/crontab | grep du > 30 19 * * 5 root /usr/bin/du -s /etc >> /tmp/lele > root@zion# date > Fri Feb 9 19:29:30 BRST 2007 > root@zion# cat /tmp/lele > 5088 /etc > root@zion# du -s /etc > 2544 /etc > > What gives that when "/usr/bin/du -s" is running from crontab is gives > the exact double of entries in the directory but when it is running > from console itself, it doesnt display the same amount of > entries!?!?!?! du uses the BLOCKSIZE environment variable to decide what size blocks to display. Crontab commands don't run with your environment; they run with a very restricted one. This is documented in the du manual page. > Weird bug... Someone probably set BLOCKSIZE in your environment. Try using "du -sk" to force du to use 1k blocks. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 22:49:40 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45ACF16A403 for ; Fri, 9 Feb 2007 22:49:40 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.228]) by mx1.freebsd.org (Postfix) with ESMTP id 07BEB13C467 for ; Fri, 9 Feb 2007 22:49:39 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: by wr-out-0506.google.com with SMTP id 69so1202156wra for ; Fri, 09 Feb 2007 14:49:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DOSuwzA++TOFDfuz/fzeP9w+2JTQn6OF+xQdBVP6u6kzZcAIVOVfg7fqDSfQRZEMglNXSWyRIlhXs72HQivysxZVdUg6m0Fn9X+2hY3/OTAN3eA5Ed6FagbxADDMsMaSVtPnF4CysAu2FSr8DSGYufXJSIlg2EL7U4u7PfUW0LE= Received: by 10.114.175.16 with SMTP id x16mr6409492wae.1171061378859; Fri, 09 Feb 2007 14:49:38 -0800 (PST) Received: by 10.114.175.5 with HTTP; Fri, 9 Feb 2007 14:49:38 -0800 (PST) Message-ID: Date: Fri, 9 Feb 2007 20:49:38 -0200 From: "Victor Loureiro Lima" To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org In-Reply-To: <205542.91900.qm@web30309.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <205542.91900.qm@web30309.mail.mud.yahoo.com> Cc: Subject: Re: /usr/bin/du + crontab weird bug X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 22:49:40 -0000 2007/2/9, R. B. Riddick : > --- Victor Loureiro Lima wrote: > > root@zion# du -s /etc > > 2544 /etc > > > > What gives that when "/usr/bin/du -s" is running from crontab is gives > > the exact double of entries in the directory but when it is running > > from console itself, it doesnt display the same amount of > > entries!?!?!?! > > > I think, it is about block size: > in the crontab environment block size is 512B and in ur shell it is 1024B. > > There is an environment variable: BLOCKSIZE > and there is an option: -k > > Just try "du -ks /etc" in ur crontab... > > -Arne Solved!!! Thanks! victor loureiro lima From owner-freebsd-fs@FreeBSD.ORG Fri Feb 9 23:31:44 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F16B16A40E for ; Fri, 9 Feb 2007 23:31:44 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: from web58602.mail.re3.yahoo.com (web58602.mail.re3.yahoo.com [68.142.236.200]) by mx1.freebsd.org (Postfix) with SMTP id CC1F813C4B2 for ; Fri, 9 Feb 2007 23:31:43 +0000 (UTC) (envelope-from aronesimi@yahoo.com) Received: (qmail 21904 invoked by uid 60001); 9 Feb 2007 23:31:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ezuAXGN1WPY21ktWyMG6ki7lSPDb5so0ZUUXvPBWvfhXH3G9wfunFfPOwTORTEWZ5Zy/qKg1KtZeou+H3cGfAXJC48Fd4ZPhvPFsNd2xI8MqAKsP1WRYRf2qQW8S8DlrDIsADLhzcWjMitDArmxr1sUTT85DMqKIL5B4yTr8Kh0=; X-YMail-OSG: 1EyvuUcVM1lVcavcI2Enw.aFbX8tig0PfFV3zNHp0MmnSM6uCoK4Cy8yFsFqT7FPY6VkaUV0v7cHHja7HvrC.rR9o2K0YUehr3a7nKa4JgSlxy8ckPl47g-- Received: from [71.136.246.192] by web58602.mail.re3.yahoo.com via HTTP; Fri, 09 Feb 2007 15:31:43 PST Date: Fri, 9 Feb 2007 15:31:43 -0800 (PST) From: Arone Silimantia To: freebsd-fs@freebsd.org MIME-Version: 1.0 Message-ID: <391245.1485.qm@web58602.mail.re3.yahoo.com> X-Mailman-Approved-At: Sat, 10 Feb 2007 00:02:27 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 23:31:44 -0000 On Fri, 9 Feb 2007, Eric Anderson wrote: > I have 5 10Tb file systems (and some 2Tb ones, but who cares about those > tiny things? :)), and I can tell you that an empty huge file system is > pretty easily fsck-able, but a full one will kill you. It greatly > depends on how many files (inodes) you have used on the file system. If > you have a massive amount of small files, you'll be eating up a ton of > memory. My 'rule of thumb' for my data (which averages to about > 16k/file) is 1G of memory for each 1Tb of disk space used. So, on a > 10Tb file system, if I ever want the fsck to complete, I need an AMD64 > box with *at least* 10G of memory, plus a lot of time. A *lot* of time. > By 'a lot', I mean anywhere from a day, to several days. So ... the time it takes to fsck is not a function of how many inodes are actually initialized from newfs, but how many you are _actually using_ ? But the amount of memory the fsck takes is a function of how many inodes exist, regardless of how many you are actually using ? Are those two interpretations correct ? --------------------------------- Everyone is raving about the all-new Yahoo! Mail beta. From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 01:42:30 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2E7816A40B for ; Sat, 10 Feb 2007 01:42:30 +0000 (UTC) (envelope-from chris@sigd.net) Received: from ms05.mailstreet2003.net (ms05.mailstreet2003.net [69.25.50.235]) by mx1.freebsd.org (Postfix) with ESMTP id B3CDD13C4A8 for ; Sat, 10 Feb 2007 01:42:30 +0000 (UTC) (envelope-from chris@sigd.net) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 9 Feb 2007 20:30:26 -0500 Message-ID: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: UFS2 with SAN Thread-Index: AcdMswv23r5T5CpjSPaH7LuLUiC+JA== From: "Chris Haulmark" To: Subject: UFS2 with SAN X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 01:42:31 -0000 Hello, I am looking into setting up a SAN with several web servers that will be clustered. It would be a FC network using Qlogic cards in each of those FreeBSD web servers. It would be about 5+ of those web servers. I want to have the capability to share the same web data across those web servers. I have scorched the entire mailing list and=20 found that there were some work on GFS porting over to FreeBSD. It seems like that it is just all talk and if I am wrong, could you have my head turned over to where I can find out how to enable GFS on those FreeBSD systems. If GFS is out of question, which file system am I recommendeded to attempt to use for this SAN setup? My first thought to use UFS2 and attempt is to allow only one web server to have a write/read access while the reminder would be read only access. That should prevent from lockings that is similar on NFS/NAS. Chris From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 01:54:14 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D8F4C16A4DC for ; Sat, 10 Feb 2007 01:54:14 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from fallbackmx03.syd.optusnet.com.au (fallbackmx03.syd.optusnet.com.au [211.29.133.136]) by mx1.freebsd.org (Postfix) with ESMTP id CD7A013C471 for ; Sat, 10 Feb 2007 01:54:13 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from mail05.syd.optusnet.com.au (mail05.syd.optusnet.com.au [211.29.132.186]) by fallbackmx03.syd.optusnet.com.au (8.12.11.20060308/8.12.11) with ESMTP id l1A07dPl023469; Sat, 10 Feb 2007 11:07:40 +1100 Received: from [127.0.0.1] (c211-30-198-155.thorn1.nsw.optusnet.com.au [211.30.198.155]) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l1A05gib022279; Sat, 10 Feb 2007 11:05:45 +1100 Message-ID: <45CD0C5A.3070804@mawer.org> Date: Fri, 09 Feb 2007 14:05:46 -1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Eric Anderson References: <646424.65334.qm@web58613.mail.re3.yahoo.com> <45CC793F.7090003@freebsd.org> In-Reply-To: <45CC793F.7090003@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Ivan Voras Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 01:54:14 -0000 On 9/02/2007 3:38 AM, Eric Anderson wrote: >> Only "collateral" problems because of the partition size: a regular >> (non-softupdates) fsck will take a LONG time to finish and eat a LOT of >> memory while it's doing its stuff. You'll need a lot of swap space (1GB >> per TB? someone had empirical numbers on this, I'm sure) if you think >> you'll need to fsck it entirely. Creating snapshots will also take a >> long time on it, and you probably want to search the lists for >> recommendations about creating snapshots in a second level directory in >> order not to block the root directory. Related to this is >> background-fsck which works by creating snapshots, so you'll probably >> want to disable it. > > I have 5 10Tb file systems (and some 2Tb ones, but who cares about those > tiny things? :)), and I can tell you that an empty huge file system is > pretty easily fsck-able, but a full one will kill you. It greatly > depends on how many files (inodes) you have used on the file system. If > you have a massive amount of small files, you'll be eating up a ton of > memory. My 'rule of thumb' for my data (which averages to about > 16k/file) is 1G of memory for each 1Tb of disk space used. So, on a > 10Tb file system, if I ever want the fsck to complete, I need an AMD64 > box with *at least* 10G of memory, plus a lot of time. A *lot* of time. > By 'a lot', I mean anywhere from a day, to several days. Has anyone looked at the changes in DragonFly that were made in the 1.8 release? I noticed the other day, reading the release notes (http://www.dragonflybsd.org/community/release1_8.shtml) the point: "Greatly reduce the memory allocated by fsck when fscking filesytems with a huge number of directories (primarily mirors with lots of hardlinked files). Otherwise fsck can run out of memory on such filesystems." Whether or not this helps in the general case, or only the scenario described, I do not know... but it would be interesting for someone with enough filesystem-foo to have a look at! --Antony From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 02:35:32 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 529DD16A401 for ; Sat, 10 Feb 2007 02:35:32 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id E3DDE13C467 for ; Sat, 10 Feb 2007 02:35:31 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so66399ugh for ; Fri, 09 Feb 2007 18:35:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pykw0lQrTspqIOeGXrqNNz1wNPb3qz2IMNUGgqPfa1SCE41i2ectuwgziY5d3lI72bodsR5q5NX5s4o+WGvLHr56Crwk/x09mZ49j/D2+6S2+FAipx0fp7gBgtQQ5Tb+y+QX/LaUGcAjU8hncaLoX9glnj9sWmD6QRVabs9Yu2Q= Received: by 10.78.17.4 with SMTP id 4mr5210000huq.1171073449096; Fri, 09 Feb 2007 18:10:49 -0800 (PST) Received: by 10.78.17.18 with HTTP; Fri, 9 Feb 2007 18:10:49 -0800 (PST) Message-ID: Date: Sat, 10 Feb 2007 02:10:49 +0000 From: "Jeff Mohler" To: "Chris Haulmark" In-Reply-To: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> MIME-Version: 1.0 References: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with SAN X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 02:35:32 -0000 ...you format a SAN target with UFS2, nobody else can touch it..think of it as a SATA drive. How many computers can plug into the same SATA drive? If you wanna share, youre looking at NFS somewhere in there. On 2/10/07, Chris Haulmark wrote: > > Hello, > > I am looking into setting up a SAN with several web servers that > will be clustered. It would be a FC network using Qlogic cards > in each of those FreeBSD web servers. It would be about 5+ > of those web servers. > > I want to have the capability to share the same web data across > those web servers. I have scorched the entire mailing list and > found that there were some work on GFS porting over to FreeBSD. > It seems like that it is just all talk and if I am wrong, could > you have my head turned over to where I can find out how to enable > GFS on those FreeBSD systems. > > If GFS is out of question, which file system am I recommendeded > to attempt to use for this SAN setup? > > My first thought to use UFS2 and attempt is to allow only one web > server to have a write/read access while the reminder would be > read only access. That should prevent from lockings that is similar > on NFS/NAS. > > Chris > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 06:48:11 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 69B2616A402 for ; Sat, 10 Feb 2007 06:48:11 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3E33913C461 for ; Sat, 10 Feb 2007 06:48:11 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l1A6m9cv091085; Sat, 10 Feb 2007 00:48:09 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45CD6AA6.1000003@freebsd.org> Date: Sat, 10 Feb 2007 00:48:06 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Chris Haulmark References: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> In-Reply-To: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2545/Fri Feb 9 14:26:25 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with SAN X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 06:48:11 -0000 On 02/09/07 19:30, Chris Haulmark wrote: > Hello, > > I am looking into setting up a SAN with several web servers that > will be clustered. It would be a FC network using Qlogic cards > in each of those FreeBSD web servers. It would be about 5+ > of those web servers. > > I want to have the capability to share the same web data across > those web servers. I have scorched the entire mailing list and > found that there were some work on GFS porting over to FreeBSD. > It seems like that it is just all talk and if I am wrong, could > you have my head turned over to where I can find out how to enable > GFS on those FreeBSD systems. GFS on FreeBSD is indeed dead. Not enough people stepped up to help port it. > If GFS is out of question, which file system am I recommendeded > to attempt to use for this SAN setup? NFS. > My first thought to use UFS2 and attempt is to allow only one web > server to have a write/read access while the reminder would be > read only access. That should prevent from lockings that is similar > on NFS/NAS. This will result it the read/write system seeing the data ok, and the rest getting corrupt data without knowing it, and probably crashing. UFS2 is not cluster aware. You could mount all the hosts read only, and then update the mount point on one to rw, makes changes, then back to ro, then unmount/remount on the other boxes. That's all still a kludge to simulate what NFS will do for you. Why won't NFS work for you? I agree that it would be fantastic to have a clustered file system for FreeBSD, and I've done lot's of hunting and nagging vendors to support it - but it's just not there. Eric From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 06:55:00 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5AECB16A400 for ; Sat, 10 Feb 2007 06:55:00 +0000 (UTC) (envelope-from chris@sigd.net) Received: from ms05.mailstreet2003.net (ms05.mailstreet2003.net [69.25.50.235]) by mx1.freebsd.org (Postfix) with ESMTP id 252AE13C481 for ; Sat, 10 Feb 2007 06:54:58 +0000 (UTC) (envelope-from chris@sigd.net) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sat, 10 Feb 2007 01:54:57 -0500 Message-ID: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB0@ms05.mailstreet2003.net> In-Reply-To: <45CD6AA6.1000003@freebsd.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: UFS2 with SAN Thread-Index: AcdM33PklpyQxGTHRpOEntCWUSYUnwAACJag References: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> <45CD6AA6.1000003@freebsd.org> From: "Chris Haulmark" To: "Eric Anderson" Cc: freebsd-fs@freebsd.org Subject: RE: UFS2 with SAN X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 06:55:00 -0000 > -----Original Message----- > From: Eric Anderson [mailto:anderson@freebsd.org] > Sent: Saturday, February 10, 2007 12:48 AM > To: Chris Haulmark > Cc: freebsd-fs@freebsd.org > Subject: Re: UFS2 with SAN >=20 > On 02/09/07 19:30, Chris Haulmark wrote: > > Hello, > > > > I am looking into setting up a SAN with several web servers that > > will be clustered. It would be a FC network using Qlogic cards > > in each of those FreeBSD web servers. It would be about 5+ > > of those web servers. > > > > I want to have the capability to share the same web data across > > those web servers. I have scorched the entire mailing list and > > found that there were some work on GFS porting over to FreeBSD. > > It seems like that it is just all talk and if I am wrong, could > > you have my head turned over to where I can find out how to enable > > GFS on those FreeBSD systems. >=20 > GFS on FreeBSD is indeed dead. Not enough people stepped up to help > port it. I really feared to hear that! >=20 > > If GFS is out of question, which file system am I recommendeded > > to attempt to use for this SAN setup? >=20 > NFS. >=20 > > My first thought to use UFS2 and attempt is to allow only one web > > server to have a write/read access while the reminder would be > > read only access. That should prevent from lockings that is similar > > on NFS/NAS. >=20 > This will result it the read/write system seeing the data ok, and the > rest getting corrupt data without knowing it, and probably crashing. > UFS2 is not cluster aware. You could mount all the hosts read only, > and > then update the mount point on one to rw, makes changes, then back to > ro, then unmount/remount on the other boxes. That's my original idea if I do not have anything else better to go with. >=20 > That's all still a kludge to simulate what NFS will do for you. Why > won't NFS work for you? I have a client who wants to go from NAS to a true SAN solution with full fibre channel network. I would hate to lose the opportunity for this client to continue using FreeBSD as the choice of OS for his web servers. Currently, his set up is using NAS with NFS. He complains of locking files that occurs too often. I had hoped to find more better solution and make this client much more happier with all the FreeBSD support that can be provided. >=20 > I agree that it would be fantastic to have a clustered file system for > FreeBSD, and I've done lot's of hunting and nagging vendors to support > it - but it's just not there. We should get few bandwagons and get in circle. It could be likely that I could provide access for the developers to test and get whatever file system and other necessaries needed to be working. :) Thanks for your reply. >=20 > Eric From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 07:10:47 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B91B16A405 for ; Sat, 10 Feb 2007 07:10:47 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3A75C13C4A3 for ; Sat, 10 Feb 2007 07:10:47 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l1A7AjIi094982; Sat, 10 Feb 2007 01:10:45 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45CD6FF5.8070007@freebsd.org> Date: Sat, 10 Feb 2007 01:10:45 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Chris Haulmark References: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> <45CD6AA6.1000003@freebsd.org> <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB0@ms05.mailstreet2003.net> In-Reply-To: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB0@ms05.mailstreet2003.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2545/Fri Feb 9 14:26:25 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with SAN X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 07:10:47 -0000 On 02/10/07 00:54, Chris Haulmark wrote: > >> -----Original Message----- >> From: Eric Anderson [mailto:anderson@freebsd.org] >> Sent: Saturday, February 10, 2007 12:48 AM >> To: Chris Haulmark >> Cc: freebsd-fs@freebsd.org >> Subject: Re: UFS2 with SAN >> >> On 02/09/07 19:30, Chris Haulmark wrote: >>> Hello, >>> >>> I am looking into setting up a SAN with several web servers that >>> will be clustered. It would be a FC network using Qlogic cards >>> in each of those FreeBSD web servers. It would be about 5+ >>> of those web servers. >>> >>> I want to have the capability to share the same web data across >>> those web servers. I have scorched the entire mailing list and >>> found that there were some work on GFS porting over to FreeBSD. >>> It seems like that it is just all talk and if I am wrong, could >>> you have my head turned over to where I can find out how to enable >>> GFS on those FreeBSD systems. >> GFS on FreeBSD is indeed dead. Not enough people stepped up to help >> port it. > > I really feared to hear that! > >>> If GFS is out of question, which file system am I recommendeded >>> to attempt to use for this SAN setup? >> NFS. >> >>> My first thought to use UFS2 and attempt is to allow only one web >>> server to have a write/read access while the reminder would be >>> read only access. That should prevent from lockings that is similar >>> on NFS/NAS. >> This will result it the read/write system seeing the data ok, and the >> rest getting corrupt data without knowing it, and probably crashing. >> UFS2 is not cluster aware. You could mount all the hosts read only, >> and >> then update the mount point on one to rw, makes changes, then back to >> ro, then unmount/remount on the other boxes. > > That's my original idea if I do not have anything else better to go > with. > >> That's all still a kludge to simulate what NFS will do for you. Why >> won't NFS work for you? > > I have a client who wants to go from NAS to a true SAN solution with > full > fibre channel network. I would hate to lose the opportunity for this > client > to continue using FreeBSD as the choice of OS for his web servers. > Currently, > his set up is using NAS with NFS. He complains of locking files that > occurs > too often. > > I had hoped to find more better solution and make this client much more > happier > with all the FreeBSD support that can be provided. Well, I'm not sure what issues they had, but have had fantastic success with NFS and FreeBSD. FreeBSD with the right hardware and tweaks can make some NetApp boxes look weak. *cough* WAFL *cough* >> I agree that it would be fantastic to have a clustered file system for >> FreeBSD, and I've done lot's of hunting and nagging vendors to support >> it - but it's just not there. > > We should get few bandwagons and get in circle. It could be likely that > I could > provide access for the developers to test and get whatever file system > and other > necessaries needed to be working. :) The problem isn't the environment or hardware, it's developers skilled to do the work. They're all either in NDA's, off writing something else, or just too busy to provide any amount of input. Eric From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 07:12:16 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D8CDB16A400 for ; Sat, 10 Feb 2007 07:12:16 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id AC24213C48D for ; Sat, 10 Feb 2007 07:12:16 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l1A7C6RE095231; Sat, 10 Feb 2007 01:12:06 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45CD7047.3040901@freebsd.org> Date: Sat, 10 Feb 2007 01:12:07 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070204) MIME-Version: 1.0 To: Antony Mawer References: <646424.65334.qm@web58613.mail.re3.yahoo.com> <45CC793F.7090003@freebsd.org> <45CD0C5A.3070804@mawer.org> In-Reply-To: <45CD0C5A.3070804@mawer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2545/Fri Feb 9 14:26:25 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org, Ivan Voras Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 07:12:16 -0000 On 02/09/07 18:05, Antony Mawer wrote: > On 9/02/2007 3:38 AM, Eric Anderson wrote: >>> Only "collateral" problems because of the partition size: a regular >>> (non-softupdates) fsck will take a LONG time to finish and eat a LOT of >>> memory while it's doing its stuff. You'll need a lot of swap space (1GB >>> per TB? someone had empirical numbers on this, I'm sure) if you think >>> you'll need to fsck it entirely. Creating snapshots will also take a >>> long time on it, and you probably want to search the lists for >>> recommendations about creating snapshots in a second level directory in >>> order not to block the root directory. Related to this is >>> background-fsck which works by creating snapshots, so you'll probably >>> want to disable it. >> I have 5 10Tb file systems (and some 2Tb ones, but who cares about those >> tiny things? :)), and I can tell you that an empty huge file system is >> pretty easily fsck-able, but a full one will kill you. It greatly >> depends on how many files (inodes) you have used on the file system. If >> you have a massive amount of small files, you'll be eating up a ton of >> memory. My 'rule of thumb' for my data (which averages to about >> 16k/file) is 1G of memory for each 1Tb of disk space used. So, on a >> 10Tb file system, if I ever want the fsck to complete, I need an AMD64 >> box with *at least* 10G of memory, plus a lot of time. A *lot* of time. >> By 'a lot', I mean anywhere from a day, to several days. > > Has anyone looked at the changes in DragonFly that were made in the 1.8 > release? I noticed the other day, reading the release notes > (http://www.dragonflybsd.org/community/release1_8.shtml) the point: > > "Greatly reduce the memory allocated by fsck when fscking filesytems > with a huge number of directories (primarily mirors with lots of > hardlinked files). Otherwise fsck can run out of memory on such > filesystems." > > Whether or not this helps in the general case, or only the scenario > described, I do not know... but it would be interesting for someone with > enough filesystem-foo to have a look at! > > --Antony I'll check that out - didn't know about it, thanks! Eric From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 14:23:15 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6DD5916A407 for ; Sat, 10 Feb 2007 14:23:15 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from smtp.voda.cz (gw.voda.cz [212.24.154.90]) by mx1.freebsd.org (Postfix) with ESMTP id E71D513C4A3 for ; Sat, 10 Feb 2007 14:23:14 +0000 (UTC) (envelope-from indigo@voda.cz) Received: from localhost (localhost [127.0.0.1]) by smtp.voda.cz (Postfix) with ESMTP id 469CF43CE1; Sat, 10 Feb 2007 15:23:13 +0100 (CET) Received: from smtp.voda.cz ([127.0.0.1]) by localhost (mail.voda.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11883-05; Sat, 10 Feb 2007 15:23:09 +0100 (CET) Received: from spyro.eiecon.net (unknown [213.151.77.190]) by smtp.voda.cz (Postfix) with ESMTP id 5003E41C81; Sat, 10 Feb 2007 15:23:09 +0100 (CET) Date: Sat, 10 Feb 2007 15:23:08 +0100 To: "Chris Haulmark" , "Eric Anderson" From: Indigo Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-2 MIME-Version: 1.0 References: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> <45CD6AA6.1000003@freebsd.org> <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB0@ms05.mailstreet2003.net> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB0@ms05.mailstreet2003.net> User-Agent: Opera Mail/9.10 (Win32) X-Virus-Scanned: by amavisd-new at voda.cz Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with SAN X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 14:23:15 -0000 On Sat, 10 Feb 2007 07:54:57 +0100, Chris Haulmark wrote: > > >> -----Original Message----- >> From: Eric Anderson [mailto:anderson@freebsd.org] >> Sent: Saturday, February 10, 2007 12:48 AM >> To: Chris Haulmark >> Cc: freebsd-fs@freebsd.org >> Subject: Re: UFS2 with SAN >> >> On 02/09/07 19:30, Chris Haulmark wrote: >> > Hello, >> > >> > I am looking into setting up a SAN with several web servers that >> > will be clustered. It would be a FC network using Qlogic cards >> > in each of those FreeBSD web servers. It would be about 5+ >> > of those web servers. >> > >> > I want to have the capability to share the same web data across >> > those web servers. I have scorched the entire mailing list and >> > found that there were some work on GFS porting over to FreeBSD. >> > It seems like that it is just all talk and if I am wrong, could >> > you have my head turned over to where I can find out how to enable >> > GFS on those FreeBSD systems. >> >> GFS on FreeBSD is indeed dead. Not enough people stepped up to help >> port it. > > I really feared to hear that! > If it was possible to use OCFS2 then thats a cluster-fs that can handle reasonable traffic. Does it work in FreeBSD? >> >> > If GFS is out of question, which file system am I recommendeded >> > to attempt to use for this SAN setup? >> >> NFS. >> >> > My first thought to use UFS2 and attempt is to allow only one web >> > server to have a write/read access while the reminder would be >> > read only access. That should prevent from lockings that is similar >> > on NFS/NAS. >> >> This will result it the read/write system seeing the data ok, and the >> rest getting corrupt data without knowing it, and probably crashing. >> UFS2 is not cluster aware. You could mount all the hosts read only, >> and >> then update the mount point on one to rw, makes changes, then back to >> ro, then unmount/remount on the other boxes. > > That's my original idea if I do not have anything else better to go > with. > >> >> That's all still a kludge to simulate what NFS will do for you. Why >> won't NFS work for you? > > I have a client who wants to go from NAS to a true SAN solution with > full > fibre channel network. I would hate to lose the opportunity for this > client > to continue using FreeBSD as the choice of OS for his web servers. > Currently, > his set up is using NAS with NFS. He complains of locking files that > occurs > too often. > > I had hoped to find more better solution and make this client much more > happier > with all the FreeBSD support that can be provided. > >> >> I agree that it would be fantastic to have a clustered file system for >> FreeBSD, and I've done lot's of hunting and nagging vendors to support >> it - but it's just not there. > > We should get few bandwagons and get in circle. It could be likely that > I could > provide access for the developers to test and get whatever file system > and other > necessaries needed to be working. :) > > Thanks for your reply. > >> >> Eric > Vasek From owner-freebsd-fs@FreeBSD.ORG Sat Feb 10 16:53:35 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8DB516A409 for ; Sat, 10 Feb 2007 16:53:35 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 47FDB13C48D for ; Sat, 10 Feb 2007 16:53:35 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so162857ugh for ; Sat, 10 Feb 2007 08:53:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=DAvh26tt3is/6TK+AndfsJ1lBaqo2v7PCwaRf//3Qmus9aRRvNv4kloniKJodi4eIdPaU8D+c53Bd00kjK2ivT15krojuFPvRDvU6u7IhAp/7V/g/L1Kyier6g3+8bANaZ42Ydbhn9YzZbmvdOlAoLjGZ26XC2mKCQ5ovy4mB2M= Received: by 10.78.160.2 with SMTP id i2mr5272220hue.1171126414116; Sat, 10 Feb 2007 08:53:34 -0800 (PST) Received: by 10.78.17.18 with HTTP; Sat, 10 Feb 2007 08:53:34 -0800 (PST) Message-ID: Date: Sat, 10 Feb 2007 08:53:34 -0800 From: "Jeff Mohler" To: "Eric Anderson" In-Reply-To: <45CD6FF5.8070007@freebsd.org> MIME-Version: 1.0 References: <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAAE@ms05.mailstreet2003.net> <45CD6AA6.1000003@freebsd.org> <6FC9F9894A9F8C49A722CF9F2132FC2204C9DAB0@ms05.mailstreet2003.net> <45CD6FF5.8070007@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Chris Haulmark Subject: Re: UFS2 with SAN X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Feb 2007 16:53:35 -0000 Well, I'm not sure what issues they had, but have had fantastic success with NFS and FreeBSD. FreeBSD with the right hardware and tweaks can make some NetApp boxes look weak. *cough* WAFL *cough* === Eric, I look forward to your white paper on that. When will we all see it? Did you fix Fbsd's nasty ../..caching issue on the client yet?