From owner-freebsd-fs@FreeBSD.ORG Sun Jun 20 06:18:21 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96CFA16A4CE for ; Sun, 20 Jun 2004 06:18:21 +0000 (GMT) Received: from mail.FreeBSD.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46BBB43D2F for ; Sun, 20 Jun 2004 06:18:18 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 97929 invoked by uid 0); 20 Jun 2004 06:17:20 -0000 Received: from unknown (HELO beastie.frontfree.net) (218.107.145.7) by mail.FreeBSD.org.cn with AES256-SHA encrypted SMTP; 20 Jun 2004 06:17:20 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id AD3FE11730 for ; Sun, 20 Jun 2004 14:17:46 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02476-05 for ; Sun, 20 Jun 2004 14:17:46 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id ACE02115D0; Sun, 20 Jun 2004 14:17:45 +0800 (CST) Date: Sun, 20 Jun 2004 14:17:45 +0800 From: Xin LI To: freebsd-fs@FreeBSD.org Message-ID: <20040620061745.GA1996@frontfree.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.2-delphij FreeBSD 5.2-delphij #66: Tue Jun 15 11:25:44 CST 2004 root@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net Subject: Will someone please have a look at bin/61981? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jun 2004 06:18:21 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, FreeBSD-fs list, Please have a look at bin/61981 and consider either commit or close it, tha= nks :-) http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/61981 Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA1SwJOfuToMruuMARArkpAJ928sUCi4mLJuO+DcJEA2LmeP0mDACgjRNv 5pD2YAn/NHGo0bYre32UqzI= =zpN5 -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From owner-freebsd-fs@FreeBSD.ORG Mon Jun 21 09:02:22 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CEEC16A4CE for ; Mon, 21 Jun 2004 09:02:22 +0000 (GMT) Received: from cnt.korolev-net.ru (cmail.korolev-net.ru [213.85.109.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B1FE43D5C for ; Mon, 21 Jun 2004 09:02:22 +0000 (GMT) (envelope-from dado@cnt.korolev-net.ru) Received: by cnt.korolev-net.ru (Postfix, from userid 100) id 2F9163FA0CF; Mon, 21 Jun 2004 13:02:08 +0400 (MSD) Date: Mon, 21 Jun 2004 13:02:08 +0400 From: Evgenii Davidov To: freebsd-fs@freebsd.org Message-ID: <20040621090208.GE77820@korolev-net.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: ufs problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 09:02:22 -0000 dear fs-wizards i have such a problem: some groups of files get corrupted from time to time: find: /usr/src/crypto/openssl/crypto/bf/asm: Bad file descriptor find: /usr/src/crypto/openssl/crypto/bn/asm/alpha: Bad file descriptor find: /usr/src/crypto/openssl/crypto/bn/asm/alpha.works: Bad file descriptor thou they was not accessed even for reading last days fsck says "partially allocated inode" and erases them i have chaged the ide disk, and it's cable too, and plugged it in an other controller but it'd didn't help me "make -j32 buildworld" works compleetly disk activity is not high: tty ad2 fd0 md0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 72 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 3 12 7 1 76 0 8 16.91 50 0.82 0.00 0 0.00 0.00 0 0.00 3 36 24 1 36 0 8 13.48 12 0.16 0.00 0 0.00 0.00 0 0.00 2 17 13 1 66 0 8 14.16 10 0.13 0.00 0 0.00 0.00 0 0.00 2 10 8 0 79 0 8 12.48 13 0.16 0.00 0 0.00 0.00 0 0.00 1 12 10 1 76 now i want to replace ide disk with scsi but will it help me.... sorry for my english thanks Evgenii V Davidov From owner-freebsd-fs@FreeBSD.ORG Tue Jun 22 15:23:16 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C857716A4DE; Tue, 22 Jun 2004 15:23:16 +0000 (GMT) Received: from portad.se (as4-6-3.lk.bonet.se [217.215.176.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5813943D2D; Tue, 22 Jun 2004 15:23:15 +0000 (GMT) (envelope-from c4@portad.se) Received: from na.portad.se (na.nat.portad.se [10.0.0.2]) by portad.se (8.12.9/8.12.9) with ESMTP id i5MFN7pE002918; Tue, 22 Jun 2004 17:23:07 +0200 (CEST) (envelope-from c4@portad.se) Message-Id: <6.0.1.1.2.20040622171402.026372d0@portad.se> X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Tue, 22 Jun 2004 17:23:18 +0200 To: freebsd-current@freebsd.org, fs@freebsd.org From: Tobias Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on portad.se Subject: Terabyte-FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 15:23:16 -0000 Okay heres another of those "we cant use terabyte filesystem"-reports again... :) vinum -> create -f /etc/vinum.conf 13 drives: D 200a State: up /dev/ad2s1d A: 0/194474 MB (0%) D 200b State: up /dev/ad4s1d A: 0/194474 MB (0%) D 200c State: up /dev/ad5s1d A: 0/194474 MB (0%) D 200d State: up /dev/ad6s1d A: 0/194474 MB (0%) D 200e State: up /dev/ad7s1d A: 0/194474 MB (0%) D 120a State: up /dev/ad8s1d A: 0/117796 MB (0%) D 120b State: up /dev/ad9s1d A: 0/117796 MB (0%) D 120c State: up /dev/ad10s1d A: 0/117796 MB (0%) D 120d State: up /dev/ad11s1d A: 0/117796 MB (0%) D 120e State: up /dev/ad12s1d A: 0/117796 MB (0%) D 120f State: up /dev/ad13s1d A: 0/117796 MB (0%) D 120g State: up /dev/ad14s1d A: 0/117796 MB (0%) D 120h State: up /dev/ad15s1d A: 0/117796 MB (0%) 1 volumes: V fetus State: up Plexes: 1 Size: 1869 GB 1 plexes: P fetus.p0 C State: up Subdisks: 13 Size: 1869 GB 13 subdisks: S fetus.p0.s0 State: up D: 200a Size: 189 GB S fetus.p0.s1 State: up D: 200b Size: 189 GB S fetus.p0.s2 State: up D: 200c Size: 189 GB S fetus.p0.s3 State: up D: 200d Size: 189 GB S fetus.p0.s4 State: up D: 200e Size: 189 GB S fetus.p0.s5 State: up D: 120a Size: 115 GB S fetus.p0.s6 State: up D: 120b Size: 115 GB S fetus.p0.s7 State: up D: 120c Size: 115 GB S fetus.p0.s8 State: up D: 120d Size: 115 GB S fetus.p0.s9 State: up D: 120e Size: 115 GB S fetus.p0.s10 State: up D: 120f Size: 115 GB S fetus.p0.s11 State: up D: 120g Size: 115 GB S fetus.p0.s12 State: up D: 120h Size: 115 GB (root@st1:~) newfs -O 2 /dev/vinum/fetus /dev/vinum/fetus: 1914745.1MB (3921397976 sectors) block size 16384, fragment size 2048 using 10420 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. newfs: can't read old UFS1 superblock: read error from block device: Invalid argument (root@st1:~) uname -a FreeBSD st1 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 I also got the same message with 5.1-RELEASE so... One solution would be to divide it into two parts... like all the 200gb drives on one end and the rest on another, but it would be much nicer to have it all as one unit. I'll try the latest -CURRENT later tonight and see if anything has changed until that not that I think so. From owner-freebsd-fs@FreeBSD.ORG Tue Jun 22 15:33:16 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C16C16A4CE; Tue, 22 Jun 2004 15:33:16 +0000 (GMT) Received: from portad.se (as4-6-3.lk.bonet.se [217.215.176.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E9C343D48; Tue, 22 Jun 2004 15:33:15 +0000 (GMT) (envelope-from c4@portad.se) Received: from na.portad.se (na.nat.portad.se [10.0.0.2]) by portad.se (8.12.9/8.12.9) with ESMTP id i5MFX7pE003039; Tue, 22 Jun 2004 17:33:07 +0200 (CEST) (envelope-from c4@portad.se) Message-Id: <6.0.1.1.2.20040622173312.02841ee0@portad.se> X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Tue, 22 Jun 2004 17:33:19 +0200 To: freebsd-current@freebsd.org, fs@freebsd.org From: Tobias Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on portad.se Subject: Terabyte-FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 15:33:16 -0000 Okay heres another of those "we cant use terabyte filesystem"-reports again... :) vinum -> create -f /etc/vinum.conf 13 drives: D 200a State: up /dev/ad2s1d A: 0/194474 MB (0%) D 200b State: up /dev/ad4s1d A: 0/194474 MB (0%) D 200c State: up /dev/ad5s1d A: 0/194474 MB (0%) D 200d State: up /dev/ad6s1d A: 0/194474 MB (0%) D 200e State: up /dev/ad7s1d A: 0/194474 MB (0%) D 120a State: up /dev/ad8s1d A: 0/117796 MB (0%) D 120b State: up /dev/ad9s1d A: 0/117796 MB (0%) D 120c State: up /dev/ad10s1d A: 0/117796 MB (0%) D 120d State: up /dev/ad11s1d A: 0/117796 MB (0%) D 120e State: up /dev/ad12s1d A: 0/117796 MB (0%) D 120f State: up /dev/ad13s1d A: 0/117796 MB (0%) D 120g State: up /dev/ad14s1d A: 0/117796 MB (0%) D 120h State: up /dev/ad15s1d A: 0/117796 MB (0%) 1 volumes: V fetus State: up Plexes: 1 Size: 1869 GB 1 plexes: P fetus.p0 C State: up Subdisks: 13 Size: 1869 GB 13 subdisks: S fetus.p0.s0 State: up D: 200a Size: 189 GB S fetus.p0.s1 State: up D: 200b Size: 189 GB S fetus.p0.s2 State: up D: 200c Size: 189 GB S fetus.p0.s3 State: up D: 200d Size: 189 GB S fetus.p0.s4 State: up D: 200e Size: 189 GB S fetus.p0.s5 State: up D: 120a Size: 115 GB S fetus.p0.s6 State: up D: 120b Size: 115 GB S fetus.p0.s7 State: up D: 120c Size: 115 GB S fetus.p0.s8 State: up D: 120d Size: 115 GB S fetus.p0.s9 State: up D: 120e Size: 115 GB S fetus.p0.s10 State: up D: 120f Size: 115 GB S fetus.p0.s11 State: up D: 120g Size: 115 GB S fetus.p0.s12 State: up D: 120h Size: 115 GB (root@st1:~) newfs -O 2 /dev/vinum/fetus /dev/vinum/fetus: 1914745.1MB (3921397976 sectors) block size 16384, fragment size 2048 using 10420 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. newfs: can't read old UFS1 superblock: read error from block device: Invalid argument (root@st1:~) uname -a FreeBSD st1 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 I also got the same message with 5.1-RELEASE so... One solution would be to divide it into two parts... like all the 200gb drives on one end and the rest on another, but it would be much nicer to have it all as one unit. I'll try the latest -CURRENT later tonight and see if anything has changed until that not that I think so. From owner-freebsd-fs@FreeBSD.ORG Tue Jun 22 21:58:57 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4B5316A4CE for ; Tue, 22 Jun 2004 21:58:57 +0000 (GMT) Received: from web13124.mail.yahoo.com (web13124.mail.yahoo.com [216.136.174.142]) by mx1.FreeBSD.org (Postfix) with SMTP id 7F6FC43D5D for ; Tue, 22 Jun 2004 21:58:57 +0000 (GMT) (envelope-from k_tutorials@yahoo.com) Message-ID: <20040622215833.80037.qmail@web13124.mail.yahoo.com> Received: from [209.213.198.25] by web13124.mail.yahoo.com via HTTP; Tue, 22 Jun 2004 14:58:33 PDT Date: Tue, 22 Jun 2004 14:58:33 -0700 (PDT) From: Krishna Monian To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: File Logging for Mac OS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 21:58:57 -0000 Hi All, I am in the process of writing a file logging utility that monitors all the files in a particular directory and prints out those files that have been accessed (read, create, delete, failed access). It is my understanding that the FreeBSD file system, which is the one used in the Darwin kernel of Mac OS is stackable. Hence I should be able to write a layer on top to do this. Is this the best way to go about what I am trying to achieve? Or are there better ways? Ideally I should be able to start and stop the logging whenever I need to. Also I would like to get the absolute path when logging as compared to a relative path. Thanks in advance Krishna Monian __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail From owner-freebsd-fs@FreeBSD.ORG Wed Jun 23 04:23:23 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A002716A4CE for ; Wed, 23 Jun 2004 04:23:23 +0000 (GMT) Received: from f19.mail.ru (f19.mail.ru [194.67.57.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B61643D2D for ; Wed, 23 Jun 2004 04:23:23 +0000 (GMT) (envelope-from shmukler@mail.ru) Received: from mail by f19.mail.ru with local id 1BczI9-0002xh-00; Wed, 23 Jun 2004 08:23:21 +0400 Received: from [24.184.137.115] by msg.mail.ru with HTTP; Wed, 23 Jun 2004 08:23:21 +0400 From: Igor Shmukler To: k_tutorials@yahoo.com Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [24.184.137.115] Date: Wed, 23 Jun 2004 08:23:21 +0400 In-Reply-To: <20040622215833.80037.qmail@web13124.mail.yahoo.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: cc: freebsd-fs@freebsd.org Subject: Re: File Logging for Mac OS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Igor Shmukler List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 04:23:23 -0000 > It is my understanding that the FreeBSD file system, > which is the one used in the Darwin kernel of Mac OS > is stackable. Hence I should be able to write a layer > on top to do this. I think you are wrong. FreeBSD has leaf file systems. It least that it currectly the case with OS X (based on older [Free]BSD [VFS]). Apple had a sample stackable fs - webdavfs, but they currently do not support stackable file systems. Look through darwin-development mailing list for details. Usually, OS X installations mean that you would be running HFS[+]. It's a very cool file system that has interesting features, but it is implementament as leaf fs as well. Check out relevant documentation. Apple advises that VFS interfaces are in transitional fase. IS. From owner-freebsd-fs@FreeBSD.ORG Fri Jun 25 12:10:30 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB67D16A4CE; Fri, 25 Jun 2004 12:10:30 +0000 (GMT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A99C43D45; Fri, 25 Jun 2004 12:10:30 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from melfina.ninth-nine.com ([IPv6:2002:d312:f91e::1]) (authenticated bits=0) by sakura.ninth-nine.com (8.12.11/8.12.11/NinthNine) with ESMTP id i5PCANhM029322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jun 2004 21:10:23 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Fri, 25 Jun 2004 21:10:23 +0900 From: Norikatsu Shigemura To: yar@FreeBSD.org Message-Id: <20040625211023.5fd5f661.nork@FreeBSD.org> X-Mailer: Sylpheed version 0.9.11-gtk2-20040613 (GTK+ 2.4.3; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Message not sent from an IPv4 address, not delayed by milter-greylist-1.4 (sakura.ninth-nine.com [IPv6:2002:db7f:4a79::1]); Fri, 25 Jun 2004 21:10:24 +0900 (JS cc: freebsd-fs@FreeBSD.org Subject: How about HFS+ X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 12:10:30 -0000 Hi Yar! On recently 5-current, I couldn't compile your HFS+ codes. How about updating these?