From owner-freebsd-fs@FreeBSD.ORG Mon Jan 29 02:44:56 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 E84A016A402 for ; Mon, 29 Jan 2007 02:44:56 +0000 (UTC) (envelope-from batjohan@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.225]) by mx1.freebsd.org (Postfix) with ESMTP id B015813C441 for ; Mon, 29 Jan 2007 02:44:56 +0000 (UTC) (envelope-from batjohan@gmail.com) Received: by wr-out-0506.google.com with SMTP id 68so813744wri for ; Sun, 28 Jan 2007 18:44:56 -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=dQc1IvS1dUWrKe6C/heJj3YMbWVqnp4Q5bnxXncGd79NJSGAQO1E7fp5LbXNmEy4NAJ64GTRdaX1Z+5Wq+roO0S9Odud8a0AGhCTXR5qKniHGhyV/rOXxDdFGauzI+ctm/EhpL8LgdAMWEFJIiB4c+9W63ysDhvh9FKz0lNd8kw= Received: by 10.114.169.2 with SMTP id r2mr234250wae.1170036966192; Sun, 28 Jan 2007 18:16:06 -0800 (PST) Received: by 10.114.153.20 with HTTP; Sun, 28 Jan 2007 18:16:06 -0800 (PST) Message-ID: Date: Mon, 29 Jan 2007 03:16:06 +0100 From: "johan andersson" To: 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 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Hello recover som files 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, 29 Jan 2007 02:44:57 -0000 Hello How do i recover my files that i did had on my /dev/ad4? i did wrote rm -rf /path/to/ad4s1d/mount by mistake. can i get them back or are they gone? im running FreeBSD 6.1 . i was using UFS with soft-updates on that drive. //Johan Andersson From owner-freebsd-fs@FreeBSD.ORG Tue Jan 30 11:45:05 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 2D43716A401; Tue, 30 Jan 2007 11:45:05 +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 CA44313C4B5; Tue, 30 Jan 2007 11:45:04 +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 7171D5F72; Tue, 30 Jan 2007 11:45:03 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 1000) id 5A1AC40D4; Tue, 30 Jan 2007 11:44:59 +0000 (GMT) Date: Tue, 30 Jan 2007 11:44:59 +0000 From: Josef Karthauser To: Joe Koberg , stable@freebsd.org, fs@freebsd.org Message-ID: <20070130114459.GI2616@genius.tao.org.uk> Mail-Followup-To: Josef Karthauser , Joe Koberg , stable@freebsd.org, fs@freebsd.org References: <20070115112106.GA2304@genius.tao.org.uk> <20070115115650.GB2304@genius.tao.org.uk> <45AB9BE4.1030606@osoft.us> <20070127224749.GA8203@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BghK6+krpKHjj+jk" Content-Disposition: inline In-Reply-To: <20070127224749.GA8203@genius.tao.org.uk> User-Agent: Mutt/1.5.11 Cc: Subject: Re: mpt problems. (Re: Dell hardware raid 0 (sas5ir) or gmirror?) 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, 30 Jan 2007 11:45:05 -0000 --BghK6+krpKHjj+jk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 27, 2007 at 10:47:49PM +0000, Josef Karthauser wrote: >=20 > The error messages from mpt are attached in the file called 'messages'. > The kernel probe boot time log is attached as dmesg.log. >=20 > Jan 27 18:42:03 littoralis kernel: mpt0: QUEUE FULL EVENT: Bus 0x00 Targe= t 0x01 Depth 121 > Jan 27 18:44:01 littoralis kernel: mpt0: QUEUE FULL EVENT: Bus 0x00 Targe= t 0x00 Depth 121 > Jan 27 18:51:06 littoralis kernel: mpt0: request 0xca756328:48785 timed o= ut for ccb 0xca8f0c00 (req->ccb 0xca8f0c00) > Jan 27 18:51:06 littoralis kernel: mpt0: attempting to abort req 0xca7563= 28:48785 function 0 > Jan 27 18:51:06 littoralis kernel: mpt0: request 0xca755c28:48786 timed o= ut for ccb 0xcc213800 (req->ccb 0xcc213800) An update for anyone who's following this thread. At Matthew Jacob's suggestion I tweaked the 'camcontrol tags' settings for the drives, and with a particular choice of settings the problems goes away. So, at boot time both drives (da0|1) report that they have 255 tag openings. However you can see above in the logs that the mpt files when the depth gets to 121. If I manually set the tags for the drives to anything 120 or above the drive controller complains under load, and one of the disks goes away. If I get it to 119 the server runs all day without missing a beat. Matt suggested quirking the drives to fix this. I'm wondering though where it is that the mpt controller get the queue size of 121 from, and why the drives report 255 at boot time. Is this because the control isn't mediating this information properly, or is there a bug in the controller firmware or driver? Joe --BghK6+krpKHjj+jk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iEYEARECAAYFAkW/L7oACgkQXVIcjOaxUBaIqgCfVkw6f/AsLgSIWjG3RhowLgrp Qj0An3Fef/lsgzeZGecLkOV5DMtt5Uw2 =qAms -----END PGP SIGNATURE----- --BghK6+krpKHjj+jk-- From owner-freebsd-fs@FreeBSD.ORG Tue Jan 30 17:04:46 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 1CF6216A411; Tue, 30 Jan 2007 17:04:46 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from exchewr01.datapipe-corp.net (exchewr01.datapipe-corp.net [64.106.130.60]) by mx1.freebsd.org (Postfix) with ESMTP id BB63813C4D3; Tue, 30 Jan 2007 17:04:45 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from [10.5.0.9] ([192.168.81.31]) by exchewr01.datapipe-corp.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Jan 2007 11:51:36 -0500 Message-ID: <45BF7797.6000708@datapipe.com> Date: Tue, 30 Jan 2007 11:51:35 -0500 From: Mark Saad User-Agent: Thunderbird 1.5.0.9 (X11/20061229) MIME-Version: 1.0 To: Josef Karthauser , Joe Koberg , stable@freebsd.org, fs@freebsd.org References: <20070115112106.GA2304@genius.tao.org.uk> <20070115115650.GB2304@genius.tao.org.uk> <45AB9BE4.1030606@osoft.us> <20070127224749.GA8203@genius.tao.org.uk> <20070130114459.GI2616@genius.tao.org.uk> In-Reply-To: <20070130114459.GI2616@genius.tao.org.uk> Content-Type: multipart/mixed; boundary="------------010009030908020604010102" X-OriginalArrivalTime: 30 Jan 2007 16:51:36.0623 (UTC) FILETIME=[E7AC6BF0:01C7448E] X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: mpt problems. (Re: Dell hardware raid 0 (sas5ir) or gmirror?) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: msaad@datapipe.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2007 17:04:46 -0000 This is a multi-part message in MIME format. --------------010009030908020604010102 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello So the HP DL320G4 servers come with a similar LSI Logic SAS controller. In 6.2-RELEASE was seeing the same issue; The fix I found was a firmware update from HP HP Firmware Update 7.6.0 . After applied the mpt messages went away . I beelive this is a bug in the LSI firmware more then the FreeBSD OS, as this controller has been very odd regardless of what os I am running on it. Josef Karthauser wrote: > On Sat, Jan 27, 2007 at 10:47:49PM +0000, Josef Karthauser wrote: >> The error messages from mpt are attached in the file called 'messages'. >> The kernel probe boot time log is attached as dmesg.log. >> > >> Jan 27 18:42:03 littoralis kernel: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x01 Depth 121 >> Jan 27 18:44:01 littoralis kernel: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x00 Depth 121 >> Jan 27 18:51:06 littoralis kernel: mpt0: request 0xca756328:48785 timed out for ccb 0xca8f0c00 (req->ccb 0xca8f0c00) >> Jan 27 18:51:06 littoralis kernel: mpt0: attempting to abort req 0xca756328:48785 function 0 >> Jan 27 18:51:06 littoralis kernel: mpt0: request 0xca755c28:48786 timed out for ccb 0xcc213800 (req->ccb 0xcc213800) > > An update for anyone who's following this thread. > > At Matthew Jacob's suggestion I tweaked the 'camcontrol tags' > settings for the drives, and with a particular choice of settings > the problems goes away. > > So, at boot time both drives (da0|1) report that they have 255 tag > openings. However you can see above in the logs that the mpt files > when the depth gets to 121. If I manually set the tags for the > drives to anything 120 or above the drive controller complains under > load, and one of the disks goes away. If I get it to 119 the server > runs all day without missing a beat. > > Matt suggested quirking the drives to fix this. I'm wondering though > where it is that the mpt controller get the queue size of 121 from, and > why the drives report 255 at boot time. Is this because the control > isn't mediating this information properly, or is there a bug in the > controller firmware or driver? > > Joe -- Mark Saad msaad@datapipe.com DataPipe Managed UNIX Support --------------010009030908020604010102-- From owner-freebsd-fs@FreeBSD.ORG Tue Jan 30 17:44:19 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 DDC0716A402; Tue, 30 Jan 2007 17:44:19 +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 93BA013C48D; Tue, 30 Jan 2007 17:44:19 +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 773C35E96; Tue, 30 Jan 2007 17:44:18 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 1000) id 6326E40D4; Tue, 30 Jan 2007 17:44:14 +0000 (GMT) Date: Tue, 30 Jan 2007 17:44:14 +0000 From: Josef Karthauser To: Mark Saad Message-ID: <20070130174414.GE6751@genius.tao.org.uk> Mail-Followup-To: Josef Karthauser , Mark Saad , Joe Koberg , stable@freebsd.org, fs@freebsd.org References: <20070115112106.GA2304@genius.tao.org.uk> <20070115115650.GB2304@genius.tao.org.uk> <45AB9BE4.1030606@osoft.us> <20070127224749.GA8203@genius.tao.org.uk> <20070130114459.GI2616@genius.tao.org.uk> <45BF7797.6000708@datapipe.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HeFlAV5LIbMFYYuh" Content-Disposition: inline In-Reply-To: <45BF7797.6000708@datapipe.com> User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org, Joe Koberg , fs@freebsd.org Subject: Re: mpt problems. (Re: Dell hardware raid 0 (sas5ir) or gmirror?) 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, 30 Jan 2007 17:44:20 -0000 --HeFlAV5LIbMFYYuh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 30, 2007 at 11:51:35AM -0500, Mark Saad wrote: > Hello > So the HP DL320G4 servers come with a similar LSI=20 > Logic SAS controller. In 6.2-RELEASE was seeing the same=20 > issue; > The fix I found was a firmware update from HP HP Firmware=20 > Update 7.6.0 . After applied the mpt messages went away . > I beelive this is a bug in the LSI firmware more then the=20 > FreeBSD OS, as this controller has been very odd=20 > regardless of what os I am running on it. >=20 I can believe that. I wonder how I should put the issue to Dell so that they can understand what I'm on about and fix it! The controller appears to be a custom version, at least the card probes as Dell part not an LSIlogic part. Joe --HeFlAV5LIbMFYYuh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iEYEARECAAYFAkW/g+0ACgkQXVIcjOaxUBajNACg1zvZwt+lfQCuKMU16V4jgpaz GbwAnjBEGUZnvxC9NQyy4KPazYzvoA3s =hw7E -----END PGP SIGNATURE----- --HeFlAV5LIbMFYYuh-- From owner-freebsd-fs@FreeBSD.ORG Thu Feb 1 10:48:43 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 9E11116A401 for ; Thu, 1 Feb 2007 10:48:43 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 49DF613C467 for ; Thu, 1 Feb 2007 10:48:43 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 437DA8441F for ; Thu, 1 Feb 2007 11:24:15 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 33297-05 for ; Thu, 1 Feb 2007 11:24:10 +0100 (CET) Received: from [IPv6:::1] (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id 161778441E for ; Thu, 1 Feb 2007 11:24:10 +0100 (CET) Message-ID: <45C1BFC9.7090104@fsn.hu> Date: Thu, 01 Feb 2007 11:24:09 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5.0.9 (X11/20070124) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Subject: g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 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, 01 Feb 2007 10:48:43 -0000 Hello, I have a setup, where I have a /data filesystem with a "big" (20G) sparse file on it. This sparse file is set up with: mdconfig -a -t vnode -f /data/nfsimg and I use /dev/md0 for storing some data, shared via NFS (I needed redundant read only NFS servers, so I just sync this image to the others and mount read only on them). With the above, I get the following in the syslog: Feb 1 11:16:49 boot00a kernel: g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 Feb 1 11:16:49 boot00a kernel: g_vfs_done():md0[WRITE(offset=1928118272, length=16384)]error = 1 Feb 1 11:17:18 boot00a kernel: g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 Feb 1 11:17:18 boot00a kernel: g_vfs_done():md0[WRITE(offset=1928118272, length=16384)]error = 1 And these two lines are alternating, with the same offsets, as you can see. I use the raw device for storing the filesystem (newfs /dev/md0). Currently the image is mounted read-write and there is almost no activity on that. Any ideas about this? Thanks, -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-fs@FreeBSD.ORG Thu Feb 1 11:36:22 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 D187716A401 for ; Thu, 1 Feb 2007 11:36:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay01.kiev.sovam.com (relay01.kiev.sovam.com [62.64.120.200]) by mx1.freebsd.org (Postfix) with ESMTP id 7825D13C467 for ; Thu, 1 Feb 2007 11:36:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.227] (helo=fw.zoral.com.ua) by relay01.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1HCZjC-000Fph-82 for freebsd-fs@freebsd.org; Thu, 01 Feb 2007 13:03:50 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id l11B3MtQ044394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Feb 2007 13:03:22 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8) with ESMTP id l11B3MaT051811; Thu, 1 Feb 2007 13:03:22 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8/Submit) id l11B3LCk051810; Thu, 1 Feb 2007 13:03:21 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 1 Feb 2007 13:03:21 +0200 From: Kostik Belousov To: Attila Nagy Message-ID: <20070201110321.GF56152@deviant.kiev.zoral.com.ua> References: <45C1BFC9.7090104@fsn.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gneEPciiIl/aKvOT" Content-Disposition: inline In-Reply-To: <45C1BFC9.7090104@fsn.hu> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.88.7, clamav-milter version 0.88.7 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-0.1 required=5.0 tests=ALL_TRUSTED,SPF_NEUTRAL autolearn=failed version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on fw.zoral.com.ua X-Scanner-Signature: 1118cf21f7425d415ed61e91afc5cb63 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 733 [Feb 01 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: freebsd-fs@freebsd.org Subject: Re: g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 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, 01 Feb 2007 11:36:22 -0000 --gneEPciiIl/aKvOT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 01, 2007 at 11:24:09AM +0100, Attila Nagy wrote: > Hello, >=20 > I have a setup, where I have a /data filesystem with a "big" (20G)=20 > sparse file on it. This sparse file is set up with: > mdconfig -a -t vnode -f /data/nfsimg > and I use /dev/md0 for storing some data, shared via NFS (I needed=20 > redundant read only NFS servers, so I just sync this image to the others= =20 > and mount read only on them). >=20 > With the above, I get the following in the syslog: > Feb 1 11:16:49 boot00a kernel:=20 > g_vfs_done():md0[WRITE(offset=3D1350844416, length=3D16384)]error =3D 1 > Feb 1 11:16:49 boot00a kernel:=20 > g_vfs_done():md0[WRITE(offset=3D1928118272, length=3D16384)]error =3D 1 > Feb 1 11:17:18 boot00a kernel:=20 > g_vfs_done():md0[WRITE(offset=3D1350844416, length=3D16384)]error =3D 1 > Feb 1 11:17:18 boot00a kernel:=20 > g_vfs_done():md0[WRITE(offset=3D1928118272, length=3D16384)]error =3D 1 >=20 > And these two lines are alternating, with the same offsets, as you can=20 > see. I use the raw device for storing the filesystem (newfs /dev/md0).=20 > Currently the image is mounted read-write and there is almost no=20 > activity on that. >=20 > Any ideas about this? errno =3D=3D 1 =3D=3D EPERM (Operation not permitted). Check for this. --gneEPciiIl/aKvOT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFwcj4C3+MBN1Mb4gRAqlOAJ4uRuE0z/rG/XupTfuZJpRnsh2M7QCeLP5x zkxnSJNAvbYRfq9j1sfR5OY= =gi8z -----END PGP SIGNATURE----- --gneEPciiIl/aKvOT-- From owner-freebsd-fs@FreeBSD.ORG Thu Feb 1 13:18:59 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 AB13916A402 for ; Thu, 1 Feb 2007 13:18:59 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 68FD213C46B for ; Thu, 1 Feb 2007 13:18:59 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id E132F8441E; Thu, 1 Feb 2007 14:18:57 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 46447-04; Thu, 1 Feb 2007 14:18:52 +0100 (CET) Received: from [IPv6:::1] (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id D4C198441F; Thu, 1 Feb 2007 14:18:51 +0100 (CET) Message-ID: <45C1E8BB.2060907@fsn.hu> Date: Thu, 01 Feb 2007 14:18:51 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5.0.9 (X11/20070124) MIME-Version: 1.0 To: Kostik Belousov References: <45C1BFC9.7090104@fsn.hu> <20070201110321.GF56152@deviant.kiev.zoral.com.ua> In-Reply-To: <20070201110321.GF56152@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-fs@freebsd.org Subject: Re: g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 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, 01 Feb 2007 13:18:59 -0000 On 02/01/07 12:03, Kostik Belousov wrote: > On Thu, Feb 01, 2007 at 11:24:09AM +0100, Attila Nagy wrote: > >> Hello, >> >> I have a setup, where I have a /data filesystem with a "big" (20G) >> sparse file on it. This sparse file is set up with: >> mdconfig -a -t vnode -f /data/nfsimg >> and I use /dev/md0 for storing some data, shared via NFS (I needed >> redundant read only NFS servers, so I just sync this image to the others >> and mount read only on them). >> >> With the above, I get the following in the syslog: >> Feb 1 11:16:49 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 >> Feb 1 11:16:49 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1928118272, length=16384)]error = 1 >> Feb 1 11:17:18 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 >> Feb 1 11:17:18 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1928118272, length=16384)]error = 1 >> >> And these two lines are alternating, with the same offsets, as you can >> see. I use the raw device for storing the filesystem (newfs /dev/md0). >> Currently the image is mounted read-write and there is almost no >> activity on that. >> >> Any ideas about this? >> > > errno == 1 == EPERM (Operation not permitted). Check for this. > Sorry, my fault. I forgot to tell that I use this image regurarly for reading/writing (to host OS environments for the boot clients) without any noticeable errors, except the above lines in the syslog. So it seems that the writes are OK, at least for the purpose of booting/running about 50 machines from this image with various OS-es (even Linux). -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-fs@FreeBSD.ORG Fri Feb 2 20:05:58 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 3CE7516A401 for ; Fri, 2 Feb 2007 20:05:58 +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 A7C9E13C4A3 for ; Fri, 2 Feb 2007 20:05:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (uzyroz@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l12K5mHR017339 for ; Fri, 2 Feb 2007 21:05:55 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l12K5mli017338; Fri, 2 Feb 2007 21:05:48 +0100 (CET) (envelope-from olli) Date: Fri, 2 Feb 2007 21:05:48 +0100 (CET) Message-Id: <200702022005.l12K5mli017338@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG 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, 02 Feb 2007 21:05:55 +0100 (CET) Cc: Subject: 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: Fri, 02 Feb 2007 20:05:58 -0000 Hi The following is on a standard UFS2 file system under FreeBSD 6.2, block size 16 KB, fragsize 2 KB. The filesystems are perfectly ok and fsck-clean. There haven't been any physical disk errors either. I've got a file on my home partition that's 214848 bytes. According to math it should occupy 14 blocks. However: $ BLOCKSIZE=16K ls -s foo 15 foo I copied the file to /tmp (which is an mdfs, also UFS2 with default parameters). Same result. I created a fresh file from /dev/zero of 214848 bytes. The same. Where does the 15th block come from? Those additional 16 KB must be used for _something_ somewhere ... fsdb(8) isn't helpful either: # fsdb -r /dev/md0 fsdb (inum: 2)> ls [...] slot 7 ino 5 reclen 20: regular, `foo' fsdb (inum: 2)> inode 5 current inode: regular file I=5 MODE=100600 SIZE=214848 BTIME=Feb 2 20:46:02 2007 [0 nsec] MTIME=Feb 2 20:46:02 2007 [0 nsec] CTIME=Feb 2 20:46:02 2007 [0 nsec] ATIME=Feb 2 20:46:58 2007 [0 nsec] OWNER=root GRP=wheel LINKCNT=1 FLAGS=0 BLKCNT=1e0 GEN=ffffffffe2ca5220 0x1e0 is 224 (== 14 * 16). So fsdb(8) doesn't see the 15th block either. To confirm: 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? 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 "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman From owner-freebsd-fs@FreeBSD.ORG Fri Feb 2 23:15:06 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 33E3C16A402; Fri, 2 Feb 2007 23:15:06 +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 B40BE13C4A3; Fri, 2 Feb 2007 23:14:59 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id BB20E45CDA; Sat, 3 Feb 2007 00:14:58 +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 3201F45696; Sat, 3 Feb 2007 00:14:52 +0100 (CET) Date: Sat, 3 Feb 2007 00:14:02 +0100 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20070202231401.GB25236@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GRPZ8SYKNexpdSJ7" Content-Disposition: inline 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-current@FreeBSD.org Subject: Call for tester! vptofh change. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2007 23:15:06 -0000 --GRPZ8SYKNexpdSJ7 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. Currently we have two VFS methods: vfs_vptofh, which translates vnode to NFS file handle and vfs_fhtovp, which translates NFS file handle to vnode. Unfortunately this allows to support only one type of structure stored in v_data (without some nasty magic). That's why I'd like to move vptofh operations from VFS operations to VOP operations. By doing this I can use different vop_vptofh operation for different kinds of vnodes. In Solaris it is already done that way - we have vfs 'vget' method which does file-handle-to-vnode translation and vnode 'fid' method, which does vnode-to-file-handle translation. I need this functionality for ZFS, but it seems to be logical move in general - VFS_VPTOFH() macro takes vnode pointer as its first argument, not mount pointer as the other VFS_*() macros, so it looks like it should be a VOP in the first place. One of the possibilities was to introduce vop_vptofh method, but leave vfs_vptofh method as it is and don't touch existing file systems, but let's do it right and convert all existing file systems from the base system to use vop_vptofh. Unfortunately touching all file systems is risky, even if the change is easy and I can't test all file systems by myself.=20 The patch is compile-tested and I also tested exporting UFS, MSDOSFS, CD9660, NULLFS and ZFS over NFS with this change and it seems to work (FreeBSD as NFS server and FreeBSD and Solaris as NFS clients). I'd like to ask for testing file systems below: HPFS NTFS UDF UnionFS EXT2FS ReiserFS XFS You would need to export the file system over NFS _before_patching_the_kernel_, mount it over NFS (even locally) and run something like 'find /path/to/fs/ -print0 | xargs ls -ld'. If it works, you need to patch the kernel, recompile it, try the same operations and report the results (also success stories). The patch can be downloaded from here: http://people.freebsd.org/~pjd/patches/vptofh.patch You apply the patch from /sys/ directory: # cd /sys/ # patch < /path/to/vptofh.patch Thank you very much in advance! --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --GRPZ8SYKNexpdSJ7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFw8W5ForvXbEpPzQRAq3MAKDRD0FxbVo02LZmExcMT/j7InkLZACgtKPK dIQRSm6nne7DdyW1UHs8wtg= =lT37 -----END PGP SIGNATURE----- --GRPZ8SYKNexpdSJ7-- From owner-freebsd-fs@FreeBSD.ORG Sat Feb 3 13:36:48 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 1AB7016A402 for ; Sat, 3 Feb 2007 13:36:48 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id A0D5D13C442 for ; Sat, 3 Feb 2007 13:36:47 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id l13D2ZEW063667; Sat, 3 Feb 2007 14:02:35 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id l13D2Rx7027173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Feb 2007 14:02:27 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id l13D2RFf077603; Sat, 3 Feb 2007 14:02:27 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id l13D2Rgd077602; Sat, 3 Feb 2007 14:02:27 +0100 (CET) (envelope-from ticso) Date: Sat, 3 Feb 2007 14:02:27 +0100 From: Bernd Walter To: Oliver Fromme Message-ID: <20070203130226.GO70860@cicely12.cicely.de> References: <200702022005.l12K5mli017338@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200702022005.l12K5mli017338@lurza.secnetix.de> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: freebsd-fs@freebsd.org Subject: Re: Mysterious block count (reproducible) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2007 13:36:48 -0000 On Fri, Feb 02, 2007 at 09:05:48PM +0100, Oliver Fromme wrote: > Hi > > The following is on a standard UFS2 file system under > FreeBSD 6.2, block size 16 KB, fragsize 2 KB. The > filesystems are perfectly ok and fsck-clean. There > haven't been any physical disk errors either. > > I've got a file on my home partition that's 214848 bytes. > According to math it should occupy 14 blocks. However: > > $ BLOCKSIZE=16K ls -s foo > 15 foo > > I copied the file to /tmp (which is an mdfs, also UFS2 > with default parameters). Same result. I created a > fresh file from /dev/zero of 214848 bytes. The same. > > Where does the 15th block come from? Those additional > 16 KB must be used for _something_ somewhere ... > > fsdb(8) isn't helpful either: > > # fsdb -r /dev/md0 > fsdb (inum: 2)> ls > [...] > slot 7 ino 5 reclen 20: regular, `foo' > fsdb (inum: 2)> inode 5 > current inode: regular file > I=5 MODE=100600 SIZE=214848 > BTIME=Feb 2 20:46:02 2007 [0 nsec] > MTIME=Feb 2 20:46:02 2007 [0 nsec] > CTIME=Feb 2 20:46:02 2007 [0 nsec] > ATIME=Feb 2 20:46:58 2007 [0 nsec] > OWNER=root GRP=wheel LINKCNT=1 FLAGS=0 BLKCNT=1e0 GEN=ffffffffe2ca5220 > > 0x1e0 is 224 (== 14 * 16). So fsdb(8) doesn't see the > 15th block either. To confirm: > > 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? Don't forget the block needed for the indirect table. fsdb only shows data blocks it seems. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-fs@FreeBSD.ORG Sat Feb 3 17:42: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 ED08A16A403 for ; Sat, 3 Feb 2007 17:42:38 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (grimm.quip.cz [213.220.192.218]) by mx1.freebsd.org (Postfix) with ESMTP id AA8C613C4A3 for ; Sat, 3 Feb 2007 17:42:38 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id D22FE62DF for ; Sat, 3 Feb 2007 18:20:56 +0100 (CET) Message-ID: <45C4C478.1000003@quip.cz> Date: Sat, 03 Feb 2007 18:20:56 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 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: Sat, 03 Feb 2007 17:42:39 -0000 Hi all, a few days ago I start reading records like this in /var/log/messages Feb 3 17:27:22 roxy smartd[71846]: Device: /dev/ad6, 1 Currently unreadable (pending) sectors Feb 3 17:27:22 roxy smartd[71846]: Device: /dev/ad6, 1 Offline uncorrectable sectors ad6 is one of two drives in gmirror, so I am not so "scared" ;) Related parts of output of smartctl -a /dev/ad6 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 # 1 Extended offline Completed: read failure 10% 4118 474119936 # 2 Short offline Completed without error 00% 4115 - How can I determine which file belongs to LBA 474119936 / How can I try to write to this sector, so drive can internaly realocate this bad sector? Is there any special tools/commands to this? Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Sat Feb 3 20:57: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 CE0E416A400 for ; Sat, 3 Feb 2007 20:57:57 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (dsl081-247-049.sfo1.dsl.speakeasy.net [64.81.247.49]) by mx1.freebsd.org (Postfix) with ESMTP id 9CA6E13C4B6 for ; Sat, 3 Feb 2007 20:57:57 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (localhost.mckusick.com [127.0.0.1]) by chez.mckusick.com (8.13.8/8.13.6) with ESMTP id l13KfdEG020521; Sat, 3 Feb 2007 12:42:02 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <200702032042.l13KfdEG020521@chez.mckusick.com> To: Pawel Jakub Dawidek Date: Sat, 03 Feb 2007 12:41:39 -0800 From: Kirk McKusick Cc: freebsd-fs@freebsd.org Subject: Re: Call for tester! vptofh change. 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, 03 Feb 2007 20:57:57 -0000 I fully approve of your changing VFS_VPTOFH to being a VOP operation. I also agree that VFS_VPTOFH should go away. Though extra work as you note, it is important `infrastructure work' to keep the interface clean. I wanted to make VPTOFH a VOP operation when I first added the VFS interface to BSD, but was pursuaded not to do so because Sun had done it as a VFS operation. The idea was to make our VFS interface as compatible to Sun's as possible because many of the BSD vendors replaced our NFS implementation with Sun's and wanted to minimize the work. Kirk McKusick