From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 17:11:38 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD3A31065673 for ; Sun, 18 Jan 2009 17:11:38 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 6940C8FC19 for ; Sun, 18 Jan 2009 17:11:37 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from DSPAM-Daemon (localhost [127.0.0.1]) by mx0.deglitch.com (Postfix) with SMTP id 4F9AE8FC27 for ; Sun, 18 Jan 2009 20:11:36 +0300 (MSK) Received: from orion.SpringDaemons.com (drsun1.dialup.corbina.ru [85.21.245.235]) by mx0.deglitch.com (Postfix) with ESMTPA id B8A8B8FC18; Sun, 18 Jan 2009 20:11:35 +0300 (MSK) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id DB77B398F3; Sun, 18 Jan 2009 20:11:38 +0300 (MSK) Date: Sun, 18 Jan 2009 20:11:38 +0300 From: Stanislav Sedov To: josh.carroll@gmail.com Message-Id: <20090118201138.eeb5d9ad.stas@FreeBSD.org> In-Reply-To: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> Organization: The FreeBSD Project X-XMPP: ssedov@jabber.ru X-Voice: +7 916 849 20 23 X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Sun Jan 18 20:11:36 2009 X-DSPAM-Confidence: 1.0000 X-DSPAM-Improbability: 1 in 98689409 chance of being spam X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 497362c8967008581431178 Cc: freebsd-fs@freebsd.org, Stable , FreeBSD Subject: Re: ext2 inode size patch - RE: PR kern/124621 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, 18 Jan 2009 17:11:39 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 3 Dec 2008 17:53:43 -0500 "Josh Carroll" mentioned: > > Ok, I describe my concern once more. I do not object against the checking > > of the inode size. But, if inode size is changed, then some data is added > > to the inode, that could (and usually does, otherwise why extend it ?) > > change intrerpetation of the inode. Thus, we need a verification of the > > fact that simply ignoring added fields does not damage filesystem or > > cause user data corruption. Verification != testing. > > Let me take another crack at explaining why I think this patch is not dangerous. > > The inode size is determined by reading the following member: > > __u16 s_inode_size; > > of the ext2_super_block structure. > > I took a look at the Linux 2.6.27.7 kernel source, and indeed they do > something very similar if not the same: > > #define EXT2_INODE_SIZE(s) (EXT2_SB(s)->s_inode_size) > > If you compare to what I did: > > #define EXT2_INODE_SIZE(s) ((s)->u.ext2_sb.s_inode_size) > > This is really the same thing, since EXT2_SB is defined (in the Linux > kernel src as): > > #ifdef __KERNEL__ > #include > static inline struct ext2_sb_info *EXT2_SB(struct super_block *sb) > { > return sb->s_fs_info; > } > > And struct ext2_sb_info has the following member: > > int s_inode_size; > > Essentially, the changes I made simply query the existing information > from the filesystem, which is what the Linux kernel does as well. > > The inode size, blocks per group, etc are all defined at filesystem > creation time by mke2fs and it ensures the sanity of the relationship > between the inodes/blocks/block groups. > > The first diagram here: > > http://sunsite.nus.sg/LDP/LDP/tlk/node95.html > > Makes it clear that as long as the number of inodes per block and the > blocks per group is is sane during fs creation, looking up the inode > size as my patch does is fine, since the creation of the filesystem is > ensures a correct by construction situation. We're simply reading the > size of the inode based on the filesystem. > > I hope this is sufficient to convince some further thought about > committing this. > > For those interested in the relevant Linux kernel source, you can have > a look at line 105 of include/linux/ext2_fs.h from the linux-2.6.27.7 > kernel source. > Hi Josh! I've commited the similar patch today that should be fixing your problem. Can you check this, please? Sorry I've missed this thread in the first place. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzYsoACgkQK/VZk+smlYF3ZwCeOyVUdzrKOdu4Pg3ztAZ0QQaY GGIAnA+oL054T0EAajbfwpYSTDRKVISC =jJFT -----END PGP SIGNATURE----- !DSPAM:497362c8967008581431178! From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 17:20:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7968A106566B for ; Sun, 18 Jan 2009 17:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 685288FC0A for ; Sun, 18 Jan 2009 17:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0IHK4KN001672 for ; Sun, 18 Jan 2009 17:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0IHK4t8001671; Sun, 18 Jan 2009 17:20:04 GMT (envelope-from gnats) Date: Sun, 18 Jan 2009 17:20:04 GMT Message-Id: <200901181720.n0IHK4t8001671@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Stanislav Sedov Cc: Subject: Re: kern/128173: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stanislav Sedov List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 17:20:04 -0000 The following reply was made to PR kern/128173; it has been noted by GNATS. From: Stanislav Sedov To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/128173: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem Date: Sun, 18 Jan 2009 20:19:48 +0300 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Christophe! Can you check, please, if recent current suffers from the same problem? The patch I've committed today should solve this issue. I can give you a patch for 7.1 if you're in position to rebuild the kernel. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzZLQACgkQK/VZk+smlYGs+wCdGTrYT8G0Ptt0ICTJ5mNKcaay xIMAn0gtJN2PYsefXuna+GP6aZIVQBPa =0UUe -----END PGP SIGNATURE----- !DSPAM:497364b1967001989116225! From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 17:25:35 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8C24106567A; Sun, 18 Jan 2009 17:25:35 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BEBB38FC22; Sun, 18 Jan 2009 17:25:35 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from freefall.freebsd.org (stas@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0IHPZMn008607; Sun, 18 Jan 2009 17:25:35 GMT (envelope-from stas@freefall.freebsd.org) Received: (from stas@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0IHPZwG008603; Sun, 18 Jan 2009 17:25:35 GMT (envelope-from stas) Date: Sun, 18 Jan 2009 17:25:35 GMT Message-Id: <200901181725.n0IHPZwG008603@freefall.freebsd.org> To: christope.cap@gmail.com, stas@FreeBSD.org, freebsd-fs@FreeBSD.org From: stas@FreeBSD.org Cc: Subject: Re: kern/128173: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem 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, 18 Jan 2009 17:25:36 -0000 Synopsis: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem State-Changed-From-To: open->feedback State-Changed-By: stas State-Changed-When: Sun Jan 18 17:25:35 UTC 2009 State-Changed-Why: Ask for submitter test. http://www.freebsd.org/cgi/query-pr.cgi?pr=128173 From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 17:25:56 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 706331065672; Sun, 18 Jan 2009 17:25:56 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E70F68FC20; Sun, 18 Jan 2009 17:25:55 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from freefall.freebsd.org (stas@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0IHPtaC008729; Sun, 18 Jan 2009 17:25:55 GMT (envelope-from stas@freefall.freebsd.org) Received: (from stas@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0IHPt3x008725; Sun, 18 Jan 2009 17:25:55 GMT (envelope-from stas) Date: Sun, 18 Jan 2009 17:25:55 GMT Message-Id: <200901181725.n0IHPt3x008725@freefall.freebsd.org> To: unk.nown@unix.net, stas@FreeBSD.org, freebsd-fs@FreeBSD.org From: stas@FreeBSD.org Cc: Subject: Re: kern/125536: [ext2fs] ext 2 mounts cleanly but fails on commands like ls 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, 18 Jan 2009 17:25:56 -0000 Synopsis: [ext2fs] ext 2 mounts cleanly but fails on commands like ls State-Changed-From-To: open->feedback State-Changed-By: stas State-Changed-When: Sun Jan 18 17:25:54 UTC 2009 State-Changed-Why: Ask for submitter test. http://www.freebsd.org/cgi/query-pr.cgi?pr=125536 From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 17:26:15 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBD2A106568B; Sun, 18 Jan 2009 17:26:15 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C2D668FC0C; Sun, 18 Jan 2009 17:26:15 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from freefall.freebsd.org (stas@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0IHQFrT008826; Sun, 18 Jan 2009 17:26:15 GMT (envelope-from stas@freefall.freebsd.org) Received: (from stas@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0IHQFTK008822; Sun, 18 Jan 2009 17:26:15 GMT (envelope-from stas) Date: Sun, 18 Jan 2009 17:26:15 GMT Message-Id: <200901181726.n0IHQFTK008822@freefall.freebsd.org> To: paulf@free.fr, stas@FreeBSD.org, freebsd-fs@FreeBSD.org From: stas@FreeBSD.org Cc: Subject: Re: kern/124621: [ext3] [patch] Cannot mount ext2fs partition 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, 18 Jan 2009 17:26:16 -0000 Synopsis: [ext3] [patch] Cannot mount ext2fs partition State-Changed-From-To: open->feedback State-Changed-By: stas State-Changed-When: Sun Jan 18 17:26:15 UTC 2009 State-Changed-Why: Ask for submitter test. http://www.freebsd.org/cgi/query-pr.cgi?pr=124621 From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 17:30:03 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68B0D106564A for ; Sun, 18 Jan 2009 17:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 575038FC16 for ; Sun, 18 Jan 2009 17:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0IHU3gr009021 for ; Sun, 18 Jan 2009 17:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0IHU3H2009012; Sun, 18 Jan 2009 17:30:03 GMT (envelope-from gnats) Date: Sun, 18 Jan 2009 17:30:03 GMT Message-Id: <200901181730.n0IHU3H2009012@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Stanislav Sedov Cc: Subject: Re: kern/125536: [ext2fs] ext 2 mounts cleanly but fails on commands like ls X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stanislav Sedov List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 17:30:03 -0000 The following reply was made to PR kern/125536; it has been noted by GNATS. From: Stanislav Sedov To: james francis toy iv Cc: bug-followup@FreeBSD.org Subject: Re: kern/125536: [ext2fs] ext 2 mounts cleanly but fails on commands like ls Date: Sun, 18 Jan 2009 20:20:36 +0300 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi James! Can you check, please, if recent current suffers from the same problem? The patch I've committed today should solve this issue. I can give you a patch for 7.1 if you're in position to rebuild the kernel. Thanks! - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzZOQACgkQK/VZk+smlYHZ5gCfbKh8dbOXcrve28rKG1xifcVt +AYAnjIdLn13ZgY5tboJsPAz0YaHqH3s =P4lP -----END PGP SIGNATURE----- !DSPAM:497364e1967001660048968! From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 17:30:05 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF9D5106566B for ; Sun, 18 Jan 2009 17:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BEC188FC14 for ; Sun, 18 Jan 2009 17:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0IHU5uY009187 for ; Sun, 18 Jan 2009 17:30:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0IHU5ID009184; Sun, 18 Jan 2009 17:30:05 GMT (envelope-from gnats) Date: Sun, 18 Jan 2009 17:30:05 GMT Message-Id: <200901181730.n0IHU5ID009184@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Stanislav Sedov Cc: Subject: Re: kern/124621: [ext3] [patch] Cannot mount ext2fs partition X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stanislav Sedov List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2009 17:30:06 -0000 The following reply was made to PR kern/124621; it has been noted by GNATS. From: Stanislav Sedov To: Paul Floyd Cc: bug-followup@FreeBSD.org Subject: Re: kern/124621: [ext3] [patch] Cannot mount ext2fs partition Date: Sun, 18 Jan 2009 20:23:22 +0300 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Paul! Can you check, please, if recent current suffers from the same problem? The patch I've committed today should solve this issue. I can give you a patch for 7.1 if you're in position to rebuild the kernel. Thanks! - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzZYoACgkQK/VZk+smlYGE/ACdE+ybZzJxb/5Nb1Qi1CyILVtW 6aAAnieoGkMpBCoFvwKAE1yVWgxu5pbA =Nn7G -----END PGP SIGNATURE----- !DSPAM:49736588967004808450424! From owner-freebsd-fs@FreeBSD.ORG Mon Jan 19 01:30:45 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5716E1065672 for ; Mon, 19 Jan 2009 01:30:45 +0000 (UTC) (envelope-from brampton@gmail.com) Received: from mail-bw0-f10.google.com (mail-bw0-f10.google.com [209.85.218.10]) by mx1.freebsd.org (Postfix) with ESMTP id A1EAF8FC17 for ; Mon, 19 Jan 2009 01:30:44 +0000 (UTC) (envelope-from brampton@gmail.com) Received: by bwz3 with SMTP id 3so488408bwz.19 for ; Sun, 18 Jan 2009 17:30:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:x-google-sender-auth; bh=fwwuMnH30kZrWut6Qh6KSV4IN04mocwynxibGUETXYg=; b=QxvOuJRuf9lZ58XTpF2bTUH1A6k8O+At4MhrZRuyr0zjbF7wV4/iea2sVlNPSLtdaK OV9vZqQZCWUzYFdyQicd32xXUG2fZP5HDs2DepoBQBS+yp34xONeDFyS1MMCxbtAVsn6 HH0jzyTcCmUETqTXn1HH4dZCudm2qu1HnRVFU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=LGaWxVp/Z7vHOUNEauvxuBwqwoZIkMRZFcDxOAY+mfvMq67NGQhzSSm+5b+5cqjAW5 7qRcZctKkM1gv5dk2imca5YiDn2sC6TQgPmSIk59S16S3hAoaa8QhIlEUogKgQg8kUN6 kP6g0/twBKG3Qd5JpqrFcCXae99C+X+gliPMw= Received: by 10.223.116.10 with SMTP id k10mr1631441faq.100.1232326896137; Sun, 18 Jan 2009 17:01:36 -0800 (PST) Received: by 10.223.110.209 with HTTP; Sun, 18 Jan 2009 17:01:36 -0800 (PST) Message-ID: Date: Mon, 19 Jan 2009 01:01:36 +0000 From: "Andrew Brampton" Sender: brampton@gmail.com To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_14457_7088607.1232326896122" X-Google-Sender-Auth: 11959421ba8450ce Subject: Pseudofs and pfs_attr_t for non-process based 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, 19 Jan 2009 01:30:45 -0000 ------=_Part_14457_7088607.1232326896122 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I've recently been coding a pseudofs based file system to export data from a custom kernel module, and allow users to control the module via the file system. Anyway, I quite like how simple it is to use pseudofs, but I found one annoying "feature". If I call pfs_create_{dir, file, link} with a pfs_attr_t function pointer, my function will never be called. I tracked this problem to the function pfs_getattr inside sys/fs/pseudofs/pseudofs_vnops.c. It has the following lines of code: if (proc != NULL) { ... if (pn->pn_attr != NULL) error = pn_attr(curthread, proc, pn, vap); ... } Basically pn_attr calls my pfs_attr_t function pointer, but only if the proc != null. Now in my case none of my files are created PFS_PROCDEP flag, which mean proc will always be null. So unless you are writing a pseudofs which is dependent on the process calling it, you cannot use a pfs_attr_t function pointer, meaning I can't change the attributes on my pseudo files. Now, to fix this problem I made a very simple patch which will call pn_attr regardless of proc being null or not. By doing this I had to also make a minor change in procfs.c as it assumes a valid proc is always passed in. I'd be grateful if someone look over my patches, and advise me if this was the correct thing to do. Also I'd be interested to know why this was original coded like this? Or was it just a oversight? Just for reference there is also a few more callbacks for various file system operations, with all of them working if proc is null, with one exception, the pfs_vis_t callback. Perhaps that should also be updated also? Thanks Andrew ------=_Part_14457_7088607.1232326896122 Content-Type: application/octet-stream; name=pseudofs_vnops.patch Content-Transfer-Encoding: base64 X-Attachment-Id: f_fq4fhez20 Content-Disposition: attachment; filename=pseudofs_vnops.patch SW5kZXg6IHN5cy9mcy9wc2V1ZG9mcy9wc2V1ZG9mc192bm9wcy5jDQo9PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQotLS0g c3lzL2ZzL3BzZXVkb2ZzL3BzZXVkb2ZzX3Zub3BzLmMgICAgKHJldmlzaW9uIDE4NzQxNSkNCisr KyBzeXMvZnMvcHNldWRvZnMvcHNldWRvZnNfdm5vcHMuYyAgICAod29ya2luZyBjb3B5KQ0KQEAg LTIyNiwxNCArMjI2LDE3IEBADQogICAgICAgIGlmIChwcm9jICE9IE5VTEwpIHsNCiAgICAgICAg ICAgICAgICB2YXAtPnZhX3VpZCA9IHByb2MtPnBfdWNyZWQtPmNyX3J1aWQ7DQogICAgICAgICAg ICAgICAgdmFwLT52YV9naWQgPSBwcm9jLT5wX3VjcmVkLT5jcl9yZ2lkOw0KLSAgICAgICAgICAg ICAgIGlmIChwbi0+cG5fYXR0ciAhPSBOVUxMKQ0KLSAgICAgICAgICAgICAgICAgICAgICAgZXJy b3IgPSBwbl9hdHRyKGN1cnRocmVhZCwgcHJvYywgcG4sIHZhcCk7DQotICAgICAgICAgICAgICAg UFJPQ19VTkxPQ0socHJvYyk7DQogICAgICAgIH0gZWxzZSB7DQogICAgICAgICAgICAgICAgdmFw LT52YV91aWQgPSAwOw0KICAgICAgICAgICAgICAgIHZhcC0+dmFfZ2lkID0gMDsNCiAgICAgICAg fQ0KDQorICAgICAgIGlmIChwbi0+cG5fYXR0ciAhPSBOVUxMKQ0KKyAgICAgICAgICAgICAgIGVy cm9yID0gcG5fYXR0cihjdXJ0aHJlYWQsIHByb2MsIHBuLCB2YXApOw0KKw0KKyAgICAgICBpZihw cm9jICE9IE5VTEwpDQorICAgICAgICAgICAgICAgUFJPQ19VTkxPQ0socHJvYyk7DQorDQogICAg ICAgIFBGU19SRVRVUk4gKGVycm9yKTsNCiB9DQo= ------=_Part_14457_7088607.1232326896122 Content-Type: application/octet-stream; name=procfs.patch Content-Transfer-Encoding: base64 X-Attachment-Id: f_fq4fhxyu1 Content-Disposition: attachment; filename=procfs.patch SW5kZXg6IHN5cy9mcy9wcm9jZnMvcHJvY2ZzLmMNCj09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCi0tLSBzeXMvZnMvcHJv Y2ZzL3Byb2Nmcy5jICAgICAgKHJldmlzaW9uIDE4NzQxNSkNCisrKyBzeXMvZnMvcHJvY2ZzL3By b2Nmcy5jICAgICAgKHdvcmtpbmcgY29weSkNCkBAIC05OSw3ICs5OSw2IEBADQogaW50DQogcHJv Y2ZzX2F0dHIoUEZTX0FUVFJfQVJHUykNCiB7DQotICAgICAgIFBST0NfTE9DS19BU1NFUlQocCwg TUFfT1dORUQpOw0KDQogICAgICAgIC8qIFhYWCBpbmVmZmljaWVudCwgc3BsaXQgaW50byBzZXBh cmF0ZSBmdW5jdGlvbnMgKi8NCiAgICAgICAgaWYgKHN0cmNtcChwbi0+cG5fbmFtZSwgImN0bCIp ID09IDAgfHwNCkBAIC0xMTIsMTIgKzExMSwxNiBAQA0KICAgICAgICAgICAgc3RyY21wKHBuLT5w bl9uYW1lLCAiZnByZWdzIikgPT0gMCkNCiAgICAgICAgICAgICAgICB2YXAtPnZhX21vZGUgPSAw NjAwOw0KDQotICAgICAgIGlmICgocC0+cF9mbGFnICYgUF9TVUdJRCkgJiYgcG4tPnBuX3R5cGUg IT0gcGZzdHlwZV9wcm9jZGlyKQ0KLSAgICAgICAgICAgICAgIHZhcC0+dmFfbW9kZSA9IDA7DQor ICAgICAgIGlmIChwICE9IE5VTEwpIHsNCisgICAgICAgICAgICAgICBQUk9DX0xPQ0tfQVNTRVJU KHAsIE1BX09XTkVEKTsNCg0KLSAgICAgICB2YXAtPnZhX3VpZCA9IHAtPnBfdWNyZWQtPmNyX3Vp ZDsNCi0gICAgICAgdmFwLT52YV9naWQgPSBwLT5wX3VjcmVkLT5jcl9naWQ7DQorICAgICAgICAg ICAgICAgaWYgKChwLT5wX2ZsYWcgJiBQX1NVR0lEKSAmJiBwbi0+cG5fdHlwZSAhPSBwZnN0eXBl X3Byb2NkaXIpDQorICAgICAgICAgICAgICAgICAgICAgICB2YXAtPnZhX21vZGUgPSAwOw0KDQor ICAgICAgICAgICAgICAgdmFwLT52YV91aWQgPSBwLT5wX3VjcmVkLT5jcl91aWQ7DQorICAgICAg ICAgICAgICAgdmFwLT52YV9naWQgPSBwLT5wX3VjcmVkLT5jcl9naWQ7DQorICAgICAgIH0NCisN CiAgICAgICAgcmV0dXJuICgwKTsNCiB9DQo= ------=_Part_14457_7088607.1232326896122-- From owner-freebsd-fs@FreeBSD.ORG Mon Jan 19 11:06:57 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9411106567D for ; Mon, 19 Jan 2009 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AC7C08FC1D for ; Mon, 19 Jan 2009 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0JB6vUU062952 for ; Mon, 19 Jan 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0JB6v5c062948 for freebsd-fs@FreeBSD.org; Mon, 19 Jan 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Jan 2009 11:06:57 GMT Message-Id: <200901191106.n0JB6v5c062948@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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, 19 Jan 2009 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o bin/130105 fs [zfs] zfs send -R dumps core o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129174 fs [nfs] [zfs] [panic] NFS v3 Panic when under high load o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129084 fs [udf] [panic] udf panic: getblk: size(67584) > MAXBSIZ f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D 32 problems total. From owner-freebsd-fs@FreeBSD.ORG Tue Jan 20 16:29:45 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEBDF106566C for ; Tue, 20 Jan 2009 16:29:45 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: from mail-qy0-f17.google.com (mail-qy0-f17.google.com [209.85.221.17]) by mx1.freebsd.org (Postfix) with ESMTP id 81AC18FC1C for ; Tue, 20 Jan 2009 16:29:45 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: by qyk10 with SMTP id 10so4842492qyk.19 for ; Tue, 20 Jan 2009 08:29:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=qASRYyAMNdGuXLjfriSZ3Dcg3+tfLvo0/4Es5HWOOPE=; b=SRIBUMp+cs4oQbuENWhgW9f3siz7i3QYEAg5HYY+esfMf0TGbEyfzV0xizAsE0JbWK LjJ8bg6JAQ10qya9Wy5Op1xktZUbm4F9wlNLKesqRuQT7f9++MNDNQ8heBsAuWm+BVXu 9kwYElm8A6DosnairH52ND8AWBKDk3/H2HWVg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=t/6fy62YqsuaCmlYMpkQo0RaAfoHrsqxK+6DI96TsB9bsmJ11GDlcqViVlkxbtjN/P 6dXytIJRj9fztf6JQMOBexrVJbtVFBnrv2gIq/qBOKYNV1GX/+UQYCPdHoL1FXl6t+XQ QIJTWoqrtnMqpakWDK7C2HwMBoJhgkoRJny48= Received: by 10.215.39.6 with SMTP id r6mr281725qaj.15.1232467058383; Tue, 20 Jan 2009 07:57:38 -0800 (PST) Received: by 10.214.115.1 with HTTP; Tue, 20 Jan 2009 07:57:38 -0800 (PST) Message-ID: Date: Tue, 20 Jan 2009 09:57:38 -0600 From: "John Hendy" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: OS X/FreeBSD shared zfs partition 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, 20 Jan 2009 16:29:46 -0000 Hi, I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to share a partition for storage between the two. I looked into getting HFS+ to work on FreeBSD (http://forums.freebsd.org/showthread.php?t=1198) but did not succeed. Then I ran across these two pages: - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html - http://zfs.macosforge.org/trac/wiki I used them to successfully change my Users folder in OS X to a zfs filesystem on a partition separate from my main OS X system/boot files. Now I just want to mount that partition from FreeBSD. Is this possible? I can see the slice in /dev as ad5s3, but there's no partitions on that slice to mount (ad5s3a, for example), nor am I familiar enough with ZFS to know what it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 /media/temp' without success. zfs.ko is loaded (seen in kldstat) and gives the usual message of it being experimental and being version 6.0. In a post on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was suggested that I try 'zpool list' but that returned 'no pools available'. I tried 'zfs list' as well and got 'no datasets available'. My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on the GPT and type B4 iirc on the MBR). I used an EFI booting program called rEFIt to sync the tables - could the MBR type of the slice be the reason I can't mount it from FreeBSD? I've searched long and hard for any posts about using zfs as a way to share a partition between any two OSs, but have not found any references on how to use a zfs slice as a shared data partition. Can it only be mounted from the OS in which it was created? Any thoughts on what I might do here? Thanks much, John From owner-freebsd-fs@FreeBSD.ORG Tue Jan 20 19:29:27 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 590D01065670 for ; Tue, 20 Jan 2009 19:29:27 +0000 (UTC) (envelope-from boris.kotzev@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.188]) by mx1.freebsd.org (Postfix) with ESMTP id D47D28FC18 for ; Tue, 20 Jan 2009 19:29:26 +0000 (UTC) (envelope-from boris.kotzev@gmail.com) Received: by mu-out-0910.google.com with SMTP id i2so1779877mue.3 for ; Tue, 20 Jan 2009 11:29:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:mime-version:content-type:content-transfer-encoding :content-disposition:message-id; bh=sUhC9Jj1OcXdky89hYVjxh1q/6I2Yb7ON7z76u72tzk=; b=T8iTO2DPq3D73uBzsIrOvSWVzZdYBkjHOW+aX2ZMKYLfMRfUlmM12nx7yGtaPO6IqL 9Mb3D838Dn7ve4gtmUffdAbjK7GdD4LiQGssuPBdkPPVxqQJzE2Msy2/7P8k2RRtQNLb p2tcTWy3q9rjOLd12/5oCSTq6AqFuzqmEwoiM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; b=i2b+B4mNQPV6RrUMOoCns53wc4YA5MI68qPUDHCHEepwzMOECytE/t+Kc2klfHh2fa kyuBOjg7CxVHWoTV15OwS8C1ySRiDvrrYoNlTBoX5JCQn/BFDvoo8cr1Eq/IWbwiMr40 MytKCuFjrVlgLfpuaX9za7Tz3UBSJf0fRLwJ0= Received: by 10.103.182.3 with SMTP id j3mr1502757mup.113.1232477911168; Tue, 20 Jan 2009 10:58:31 -0800 (PST) Received: from host7.net62.hdsl-213-169.fastbg.net (host7.net62.HDSL-213-169.FastBG.NET [213.169.62.7]) by mx.google.com with ESMTPS id y6sm11159653mug.32.2009.01.20.10.58.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jan 2009 10:58:29 -0800 (PST) From: Boris Kotzev To: freebsd-fs@freebsd.org Date: Tue, 20 Jan 2009 20:58:25 +0200 User-Agent: KMail/1.10.4 (FreeBSD/8.0-CURRENT; KDE/4.1.4; amd64; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901202058.25355.boris.kotzev@gmail.com> Cc: Subject: OS X/FreeBSD shared zfs partition 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, 20 Jan 2009 19:29:27 -0000 > Hi, > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to share a > partition for storage between the two. I looked into getting HFS+ to work on > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198) > but > did not succeed. Then I ran across these two pages: > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > - http://zfs.macosforge.org/trac/wiki > > I used them to successfully change my Users folder in OS X to a zfs > filesystem on a partition separate from my main OS X system/boot files. Now > I just want to mount that partition from FreeBSD. Is this possible? I can > see the slice in /dev as ad5s3, but there's no partitions on that slice to > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know what > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and gives > the usual message of it being experimental and being version 6.0. In a post > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > suggested that I try 'zpool list' but that returned 'no pools available'. I > tried 'zfs list' as well and got 'no datasets available'. > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on the > GPT and type B4 iirc on the MBR). I used an EFI booting program called rEFIt > to sync the tables - could the MBR type of the slice be the reason I can't > mount it from FreeBSD? > > I've searched long and hard for any posts about using zfs as a way to share > a partition between any two OSs, but have not found any references on how to > use a zfs slice as a shared data partition. Can it only be mounted from the > OS in which it was created? Any thoughts on what I might do here? > > > Thanks much, > John What does zfs import return? Regards, Boris Kotzev From owner-freebsd-fs@FreeBSD.ORG Tue Jan 20 19:33:09 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12D0E106566C for ; Tue, 20 Jan 2009 19:33:09 +0000 (UTC) (envelope-from boris.kotzev@gmail.com) Received: from mail-ew0-f20.google.com (mail-ew0-f20.google.com [209.85.219.20]) by mx1.freebsd.org (Postfix) with ESMTP id 949458FC13 for ; Tue, 20 Jan 2009 19:33:08 +0000 (UTC) (envelope-from boris.kotzev@gmail.com) Received: by ewy13 with SMTP id 13so1411483ewy.19 for ; Tue, 20 Jan 2009 11:33:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:to:subject:cc :content-disposition:from:date:mime-version:content-type :content-transfer-encoding:message-id; bh=EJ8NTayFmuA4b78H5RJd44AHl5rsRHc7ldtXaFpgjj4=; b=oOzR1BXdL5OaK2uo3sJaofG5tZnuAmqxSLwdDRzqgKffwoNqAcgMLS2lcaFd2/hENP KcGy9uKG+U98+/TQz72lk7umejUc9KDBCmEflWIqLM/WDE0P/7AUHSDpxVUzKXcdB4Ed K7e2MNV5hgciNNYAQ/rF3gY3xLiLf719Dk4R8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=to:subject:cc:content-disposition:from:date:mime-version :content-type:content-transfer-encoding:message-id; b=dQOVsd1viZj9fQtqPR1oQXyyqUf+75iOsdFRMs4pQheQVxE296zJxZ8PhG8djVECx4 aLUFHSG+3rd+pSmGCghUiU1yzGYeJupDJKrkhYJTrzqv/LZvD1Brr+bjM8wx+YJKUJ3B /EmjqIwsBZOH7oP3m+FLF6oAf+ss59OMzwPbY= Received: by 10.103.247.14 with SMTP id z14mr3613mur.70.1232478091864; Tue, 20 Jan 2009 11:01:31 -0800 (PST) Received: from host7.net62.hdsl-213-169.fastbg.net (host7.net62.HDSL-213-169.FastBG.NET [213.169.62.7]) by mx.google.com with ESMTPS id i5sm6009303mue.46.2009.01.20.11.01.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jan 2009 11:01:30 -0800 (PST) To: freebsd-fs@freebsd.org Content-Disposition: inline From: Boris Kotzev Date: Tue, 20 Jan 2009 21:01:27 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200901202101.27544.boris.kotzev@gmail.com> Cc: Subject: OS X/FreeBSD shared zfs partition 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, 20 Jan 2009 19:33:09 -0000 > Hi, > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to share a > partition for storage between the two. I looked into getting HFS+ to work on > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198) > but > did not succeed. Then I ran across these two pages: > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > - http://zfs.macosforge.org/trac/wiki > > I used them to successfully change my Users folder in OS X to a zfs > filesystem on a partition separate from my main OS X system/boot files. Now > I just want to mount that partition from FreeBSD. Is this possible? I can > see the slice in /dev as ad5s3, but there's no partitions on that slice to > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know what > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and gives > the usual message of it being experimental and being version 6.0. In a post > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > suggested that I try 'zpool list' but that returned 'no pools available'. I > tried 'zfs list' as well and got 'no datasets available'. > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on the > GPT and type B4 iirc on the MBR). I used an EFI booting program called rEFIt > to sync the tables - could the MBR type of the slice be the reason I can't > mount it from FreeBSD? > > I've searched long and hard for any posts about using zfs as a way to share > a partition between any two OSs, but have not found any references on how to > use a zfs slice as a shared data partition. Can it only be mounted from the > OS in which it was created? Any thoughts on what I might do here? > > > Thanks much, > John I am sorry, I wanted to ask what zpool import returns. Regards, Boris Kotzev From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 00:08:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1B031065672 for ; Wed, 21 Jan 2009 00:08:14 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: from mail-qy0-f17.google.com (mail-qy0-f17.google.com [209.85.221.17]) by mx1.freebsd.org (Postfix) with ESMTP id 3DD848FC18 for ; Wed, 21 Jan 2009 00:08:13 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: by qyk10 with SMTP id 10so5148275qyk.19 for ; Tue, 20 Jan 2009 16:08:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=i6RJPEZqeK44GVO5O+pO13Qtdby2YYWZLi5phNth4i8=; b=aTQmSU1cfeTlBFcAmEM4hGNp2jiCTaKD1dk5fqC01oT1+YcdxhWxZo2viYD1c6v5Ke xd+STKERLHSlO92FqebXXB7UGMO96sfVLmKULRyHBoldMLIboNPe/xVE8xLVsYJWGD1g c1qtrpMIuyVWSr7HpKSkNp6htcshJUJGfcfog= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=WKp9Z0v+M1dda/qRp93edOSfSQ8+6l/9rlt2iM8Ml816U34lD4ir2p9zIzb+Vmd6DW E6CNscMnJhecpyj7eugSvNhq0WnyB6zKFuRPsIGnNdKcdq6NX22UbARGzVdUPVCqyeXR 1s9eVfIqSLT7kVCTZHq8CdeYmFzxwL+1Zs0ac= Received: by 10.214.218.18 with SMTP id q18mr4019573qag.78.1232496485352; Tue, 20 Jan 2009 16:08:05 -0800 (PST) Received: by 10.214.115.1 with HTTP; Tue, 20 Jan 2009 16:08:05 -0800 (PST) Message-ID: Date: Tue, 20 Jan 2009 18:08:05 -0600 From: "John Hendy" To: "Boris Kotzev" In-Reply-To: <200901202101.27544.boris.kotzev@gmail.com> MIME-Version: 1.0 References: <200901202101.27544.boris.kotzev@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: OS X/FreeBSD shared zfs partition 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, 21 Jan 2009 00:08:15 -0000 Wow... I really didn't expect that to work! Well, it 'kind of worked'. Here's what I got: I did 'zpool import' and got the usual 'ZFS is experimental in FreeBSD, ZFS filesystem version 6' and it said something like 'you can import pools by name' (sorry - i missed the exact message). Then I did 'zfs lilst' and tank was listed, but not tank/jwhendy. Then I did 'zfs mount tank/jwhendy' and got: 'Mismatched versions: Filesystem is version 2 on-disk format, which is incompatible with this software version 1! You can force mounting with -f' I did 'zfs mount -f tank/jwhendy' and it said 'Cannot mount 'tank/jwhendy': Operation not supported', but zfs list shows: NAME USED AVAIL REFER MOUNTPOINT tank 11.4G 27.2G 390K /tank tank/jwhendy 11.4G 27.2G 11.4G /tank/jwhendy So... it appears it mounted? when I cd /tank/jwhendy, though, all that is in the folder is a file called .autodiskmounted, which I assume is used by OS X. I think we've made some progress... any way to go the whole way? Can I upgrade the zfs version in FreeBSD since it complains about the mismatched software versions? Just a thought. Thanks! John On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev wrote: > > Hi, > > > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to > share a > > partition for storage between the two. I looked into getting HFS+ to work > on > > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< > http://forums.freebsd.org/showthread.php?t=1198> > > but > > did not succeed. Then I ran across these two pages: > > > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > > - http://zfs.macosforge.org/trac/wiki > > > > I used them to successfully change my Users folder in OS X to a zfs > > filesystem on a partition separate from my main OS X system/boot files. > Now > > I just want to mount that partition from FreeBSD. Is this possible? I can > > see the slice in /dev as ad5s3, but there's no partitions on that slice > to > > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know > what > > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and > gives > > the usual message of it being experimental and being version 6.0. In a > post > > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > > suggested that I try 'zpool list' but that returned 'no pools available'. > I > > tried 'zfs list' as well and got 'no datasets available'. > > > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on > the > > GPT and type B4 iirc on the MBR). I used an EFI booting program called > rEFIt > > to sync the tables - could the MBR type of the slice be the reason I > can't > > mount it from FreeBSD? > > > > I've searched long and hard for any posts about using zfs as a way to > share > > a partition between any two OSs, but have not found any references on how > to > > use a zfs slice as a shared data partition. Can it only be mounted from > the > > OS in which it was created? Any thoughts on what I might do here? > > > > > > Thanks much, > > John > > I am sorry, I wanted to ask what > > zpool import > > returns. > > Regards, > > Boris Kotzev > > > > > > > From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 00:12:59 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06993106566B for ; Wed, 21 Jan 2009 00:12:59 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id AB9A78FC0A for ; Wed, 21 Jan 2009 00:12:58 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: by an-out-0708.google.com with SMTP id b38so84202ana.13 for ; Tue, 20 Jan 2009 16:12:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=+TkVmLqq8z710OGAcs7zt9Auc2SXS5MCw4GgjmFeDq0=; b=ae79Kr3YvDJ4O4sFHOglnXd0sJtBE4gUty2k08ruWo7CieG4pnJo10C3EkeGtCt7d0 f7v1G42YQFAsC2BxyA6ug6KcKPYqa0AmuAzfqZ9WMglmjb4+iiWFMmHExawtDAxNvs2t 7BTC8yv4wsIKwTF9y314qo/41xg0DA2Fu/ltU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=rHg8QxswZiYHunAFSRUJM5PvwJtkKucdUhfkHE6gAs+aJl5RcS6r9NWcnRn6t7lGxd iq4Md860nxk9z/iXgOJZzoda33CrrrG3rv4pSvc9ccZAF/Xv2vm40zFCkc5uugHgROOj SQ1jFlfmcrxZVQgHtqpYzrmOZya7L73oc9IxY= Received: by 10.100.197.3 with SMTP id u3mr5290395anf.64.1232496777283; Tue, 20 Jan 2009 16:12:57 -0800 (PST) Received: by 10.100.231.10 with HTTP; Tue, 20 Jan 2009 16:12:57 -0800 (PST) Message-ID: Date: Tue, 20 Jan 2009 18:12:57 -0600 From: "John Hendy" To: "Boris Kotzev" In-Reply-To: <200901202101.27544.boris.kotzev@gmail.com> MIME-Version: 1.0 References: <200901202101.27544.boris.kotzev@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: OS X/FreeBSD shared zfs partition 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, 21 Jan 2009 00:12:59 -0000 Oh, and 'zpool status' returns: pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ad5s3 ONLINE 0 0 0 And when I just tried 'zfs unmount tank/jwhendy' I get 'cannot unmount tank/jwhendy: not currently mounted'. Just wanted to add that... I thought tank/jwhendy hendy was mounted since it's mountpoint directory was not empty, but according to zfs it was not mounted. Thanks, John On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev wrote: > > Hi, > > > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to > share a > > partition for storage between the two. I looked into getting HFS+ to work > on > > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< > http://forums.freebsd.org/showthread.php?t=1198> > > but > > did not succeed. Then I ran across these two pages: > > > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > > - http://zfs.macosforge.org/trac/wiki > > > > I used them to successfully change my Users folder in OS X to a zfs > > filesystem on a partition separate from my main OS X system/boot files. > Now > > I just want to mount that partition from FreeBSD. Is this possible? I can > > see the slice in /dev as ad5s3, but there's no partitions on that slice > to > > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know > what > > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and > gives > > the usual message of it being experimental and being version 6.0. In a > post > > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > > suggested that I try 'zpool list' but that returned 'no pools available'. > I > > tried 'zfs list' as well and got 'no datasets available'. > > > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on > the > > GPT and type B4 iirc on the MBR). I used an EFI booting program called > rEFIt > > to sync the tables - could the MBR type of the slice be the reason I > can't > > mount it from FreeBSD? > > > > I've searched long and hard for any posts about using zfs as a way to > share > > a partition between any two OSs, but have not found any references on how > to > > use a zfs slice as a shared data partition. Can it only be mounted from > the > > OS in which it was created? Any thoughts on what I might do here? > > > > > > Thanks much, > > John > > I am sorry, I wanted to ask what > > zpool import > > returns. > > Regards, > > Boris Kotzev > > > > > > > From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 02:41:07 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 171C0106567C for ; Wed, 21 Jan 2009 02:41:07 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2B1508FC0C for ; Wed, 21 Jan 2009 02:41:06 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (morganw-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:47e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 4123984CEE1B; Tue, 20 Jan 2009 20:41:03 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0L2eutc025378; Tue, 20 Jan 2009 20:40:57 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Tue, 20 Jan 2009 20:40:55 -0600 (CST) From: Wes Morgan To: John Hendy In-Reply-To: Message-ID: References: <200901202101.27544.boris.kotzev@gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, Boris Kotzev Subject: Re: OS X/FreeBSD shared zfs partition 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, 21 Jan 2009 02:41:08 -0000 On Tue, 20 Jan 2009, John Hendy wrote: > Wow... I really didn't expect that to work! Well, it 'kind of worked'. > Here's what I got: > > I did 'zpool import' and got the usual 'ZFS is experimental in FreeBSD, ZFS > filesystem version 6' and it said something like 'you can import pools by > name' (sorry - i missed the exact message). Then I did 'zfs lilst' and tank > was listed, but not tank/jwhendy. That version "6" is the pool format. The actual filesystem on-disk versions are different. In -current, the pool version is 13 and filesystem version is 3, according to both "zpool upgrade" and "zfs upgrade". Sounds like the zfs code in OS X is more recent than that in -stable. > Then I did 'zfs mount tank/jwhendy' and got: > > 'Mismatched versions: Filesystem is version 2 on-disk format, which is > incompatible with this software version 1! You can force mounting with -f' > > I did 'zfs mount -f tank/jwhendy' and it said 'Cannot mount 'tank/jwhendy': > Operation not supported', but zfs list shows: Yeah I wouldn't advice doing that, no telling what will happen. zfs list will show you filesystem status regardless of mount status, it's just reading the pool data I imagine. > > NAME USED AVAIL REFER MOUNTPOINT > tank 11.4G 27.2G 390K /tank > tank/jwhendy 11.4G 27.2G 11.4G /tank/jwhendy > > So... it appears it mounted? when I cd /tank/jwhendy, though, all that is in > the folder is a file called .autodiskmounted, which I assume is used by OS > X. > > I think we've made some progress... any way to go the whole way? Can I > upgrade the zfs version in FreeBSD since it complains about the mismatched > software versions? Just a thought. > > > > Thanks! > John > > On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev wrote: > >>> Hi, >>> >>> I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to >> share a >>> partition for storage between the two. I looked into getting HFS+ to work >> on >>> FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< >> http://forums.freebsd.org/showthread.php?t=1198> >>> but >>> did not succeed. Then I ran across these two pages: >>> >>> - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html >>> - http://zfs.macosforge.org/trac/wiki >>> >>> I used them to successfully change my Users folder in OS X to a zfs >>> filesystem on a partition separate from my main OS X system/boot files. >> Now >>> I just want to mount that partition from FreeBSD. Is this possible? I can >>> see the slice in /dev as ad5s3, but there's no partitions on that slice >> to >>> mount (ad5s3a, for example), nor am I familiar enough with ZFS to know >> what >>> it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 >>> /media/temp' without success. zfs.ko is loaded (seen in kldstat) and >> gives >>> the usual message of it being experimental and being version 6.0. In a >> post >>> on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was >>> suggested that I try 'zpool list' but that returned 'no pools available'. >> I >>> tried 'zfs list' as well and got 'no datasets available'. >>> >>> My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both >>> show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on >> the >>> GPT and type B4 iirc on the MBR). I used an EFI booting program called >> rEFIt >>> to sync the tables - could the MBR type of the slice be the reason I >> can't >>> mount it from FreeBSD? >>> >>> I've searched long and hard for any posts about using zfs as a way to >> share >>> a partition between any two OSs, but have not found any references on how >> to >>> use a zfs slice as a shared data partition. Can it only be mounted from >> the >>> OS in which it was created? Any thoughts on what I might do here? >>> >>> >>> Thanks much, >>> John >> >> I am sorry, I wanted to ask what >> >> zpool import >> >> returns. >> >> Regards, >> >> Boris Kotzev From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 04:29:45 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8CC310656CF for ; Wed, 21 Jan 2009 04:29:45 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: from mail-qy0-f17.google.com (mail-qy0-f17.google.com [209.85.221.17]) by mx1.freebsd.org (Postfix) with ESMTP id 802918FC13 for ; Wed, 21 Jan 2009 04:29:45 +0000 (UTC) (envelope-from jw.hendy@gmail.com) Received: by qyk10 with SMTP id 10so5270772qyk.19 for ; Tue, 20 Jan 2009 20:29:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=LsnN8Hk4AbvehQmR3kktk2nQNCnNvSTe2dXiRBp+a+E=; b=rnvqR5E8iEUErvBP3u81XuYS7a9tG2xTIF8+Fz+gL6s38xq09fmhVs7IwJasSFIhDd aGgv/3hiNzat869//EOKFMYihJAIBcvTJ7Ozs/kAUUaQH5ubXCGaYfO+shiD++2tMj9P mjkvWLPcDt468bCPzl/ae+q7DaOZqqOnCIydU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FpP5tSvU5zZYhOffbqiLfoXfyqVGmLPfevyDSZT5cH0NCR/3uHzPajvT+4CoOudc/R sDuA2j5jkzjGmVjVzQff0TDtkt8IVkwOYmKwS/5qOioT6W6M/f4uK3Hh7vgE7wuAWL48 J9iwywLPLQMrTGT6MI85GLwQPC9AzeD01lVkE= MIME-Version: 1.0 Received: by 10.214.216.14 with SMTP id o14mr1359219qag.229.1232512184300; Tue, 20 Jan 2009 20:29:44 -0800 (PST) In-Reply-To: References: <200901202101.27544.boris.kotzev@gmail.com> Date: Tue, 20 Jan 2009 22:29:44 -0600 Message-ID: From: John Hendy To: Jake Scott Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Boris Kotzev Subject: Re: OS X/FreeBSD shared zfs partition 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, 21 Jan 2009 04:29:46 -0000 Thanks Boris and Jake. Is this 7.0 current we're talking about, or 8.0? I'm still pretty new to FreeBSD and trying to sort the nomenclature: release, current, stable... along with each of those I believe is also a version (7.0, 7.1, 8.0, etc.). Just looking to know what I should run to have a compatible version of the filesystem. I do not want bleeding edge, so 8.0 is out... I wouldn't mind something like 7.1 stable, though. Would that be possible? Thanks, John On Tue, Jan 20, 2009 at 6:19 PM, Jake Scott wrote: > MacOS has a later version of the file system. If you don't have any data > you care about on it yet, then try re-creating the pool in FreeBSD and then > importing it into MacOS. Otherwise, you will need FreeBSD current... > > > J> > > > > > On Tue, 20 Jan 2009, John Hendy wrote: > > Oh, and 'zpool status' returns: >> >> pool: tank >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> tank ONLINE 0 0 0 >> ad5s3 ONLINE 0 0 0 >> >> And when I just tried 'zfs unmount tank/jwhendy' I get 'cannot unmount >> tank/jwhendy: not currently mounted'. Just wanted to add that... I thought >> tank/jwhendy hendy was mounted since it's mountpoint directory was not >> empty, but according to zfs it was not mounted. >> >> >> Thanks, >> John >> >> On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev > >wrote: >> >> Hi, >>>> >>>> I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to >>>> >>> share a >>> >>>> partition for storage between the two. I looked into getting HFS+ to >>>> work >>>> >>> on >>> >>>> FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< >>>> >>> http://forums.freebsd.org/showthread.php?t=1198> >>> >>>> but >>>> did not succeed. Then I ran across these two pages: >>>> >>>> - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html >>>> - http://zfs.macosforge.org/trac/wiki >>>> >>>> I used them to successfully change my Users folder in OS X to a zfs >>>> filesystem on a partition separate from my main OS X system/boot files. >>>> >>> Now >>> >>>> I just want to mount that partition from FreeBSD. Is this possible? I >>>> can >>>> see the slice in /dev as ad5s3, but there's no partitions on that slice >>>> >>> to >>> >>>> mount (ad5s3a, for example), nor am I familiar enough with ZFS to know >>>> >>> what >>> >>>> it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 >>>> /media/temp' without success. zfs.ko is loaded (seen in kldstat) and >>>> >>> gives >>> >>>> the usual message of it being experimental and being version 6.0. In a >>>> >>> post >>> >>>> on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was >>>> suggested that I try 'zpool list' but that returned 'no pools >>>> available'. >>>> >>> I >>> >>>> tried 'zfs list' as well and got 'no datasets available'. >>>> >>>> My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they >>>> both >>>> show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on >>>> >>> the >>> >>>> GPT and type B4 iirc on the MBR). I used an EFI booting program called >>>> >>> rEFIt >>> >>>> to sync the tables - could the MBR type of the slice be the reason I >>>> >>> can't >>> >>>> mount it from FreeBSD? >>>> >>>> I've searched long and hard for any posts about using zfs as a way to >>>> >>> share >>> >>>> a partition between any two OSs, but have not found any references on >>>> how >>>> >>> to >>> >>>> use a zfs slice as a shared data partition. Can it only be mounted from >>>> >>> the >>> >>>> OS in which it was created? Any thoughts on what I might do here? >>>> >>>> >>>> Thanks much, >>>> John >>>> >>> >>> I am sorry, I wanted to ask what >>> >>> zpool import >>> >>> returns. >>> >>> Regards, >>> >>> Boris Kotzev >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >> 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 Wed Jan 21 05:04:25 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE847106564A for ; Wed, 21 Jan 2009 05:04:25 +0000 (UTC) (envelope-from chris@young-alumni.com) Received: from mail.oldschoolpunx.net (cpe-72-177-10-243.austin.res.rr.com [72.177.10.243]) by mx1.freebsd.org (Postfix) with ESMTP id 8001C8FC14 for ; Wed, 21 Jan 2009 05:04:25 +0000 (UTC) (envelope-from chris@young-alumni.com) Received: by mail.oldschoolpunx.net (Postfix, from userid 58) id 6B2EF7DED4; Tue, 20 Jan 2009 22:49:11 -0600 (CST) Received: from [192.168.8.200] (unknown [192.168.8.200]) by mail.oldschoolpunx.net (Postfix) with ESMTPSA id D25047DEB8 for ; Tue, 20 Jan 2009 22:45:22 -0600 (CST) Resent-To: freebsd-fs@freebsd.org From: Chris Ruiz To: John Hendy In-Reply-To: Resent-From: Chris Ruiz References: <200901202101.27544.boris.kotzev@gmail.com> Message-Id: <818F3AAA-919C-4848-826C-4982592649FF@young-alumni.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Resent-Date: Tue, 20 Jan 2009 22:45:22 -0600 Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 22:44:12 -0600 X-Mailer: Apple Mail (2.930.3) Resent-Message-Id: <20090121044522.D25047DEB8@mail.oldschoolpunx.net> Cc: Subject: Re: OS X/FreeBSD shared zfs partition 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, 21 Jan 2009 05:04:25 -0000 On Jan 20, 2009, at 10:29 PM, John Hendy wrote: > Thanks Boris and Jake. > > Is this 7.0 current we're talking about, or 8.0? I'm still pretty > new to > FreeBSD and trying to sort the nomenclature: release, current, > stable... > along with each of those I believe is also a version (7.0, 7.1, 8.0, > etc.). > Just looking to know what I should run to have a compatible version > of the > filesystem. I do not want bleeding edge, so 8.0 is out... I wouldn't > mind > something like 7.1 stable, though. Would that be possible? 7 = STABLE, 8 = CURRENT. I have successfully used a zfs flash drive on osx 10.5.6 w/ zfs 119 and freebsd 7.1. Try setting up your zpool with osx's implementation. When you switch between operating systems, you will need to zpool import -f. Also, osx uses acls to prevent you from being able to execute anything written to your zfs filesystems from any other operating system (this shouldn't matter if you are just storing data). You shouldn't need to use mount at all, your filesystems will be auto-mounted when you import your zpool. Hope this helps, Chris Ruiz > > Thanks, > John > > On Tue, Jan 20, 2009 at 6:19 PM, Jake Scott wrote: > >> MacOS has a later version of the file system. If you don't have >> any data >> you care about on it yet, then try re-creating the pool in FreeBSD >> and then >> importing it into MacOS. Otherwise, you will need FreeBSD current... >> >> >> J> >> >> >> >> >> On Tue, 20 Jan 2009, John Hendy wrote: >> >> Oh, and 'zpool status' returns: >>> >>> pool: tank >>> state: ONLINE >>> scrub: none requested >>> config: >>> >>> NAME STATE READ WRITE CKSUM >>> tank ONLINE 0 0 0 >>> ad5s3 ONLINE 0 0 0 >>> >>> And when I just tried 'zfs unmount tank/jwhendy' I get 'cannot >>> unmount >>> tank/jwhendy: not currently mounted'. Just wanted to add that... I >>> thought >>> tank/jwhendy hendy was mounted since it's mountpoint directory was >>> not >>> empty, but according to zfs it was not mounted. >>> >>> >>> Thanks, >>> John >>> >>> On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev >>> >>> wrote: >>> >>> Hi, >>>>> >>>>> I dual boot OS X and FreeBSD (currently 7.0-i386) and have >>>>> wanted to >>>>> >>>> share a >>>> >>>>> partition for storage between the two. I looked into getting HFS >>>>> + to >>>>> work >>>>> >>>> on >>>> >>>>> FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< >>>>> >>>> http://forums.freebsd.org/showthread.php?t=1198> >>>> >>>>> but >>>>> did not succeed. Then I ran across these two pages: >>>>> >>>>> - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html >>>>> - http://zfs.macosforge.org/trac/wiki >>>>> >>>>> I used them to successfully change my Users folder in OS X to a >>>>> zfs >>>>> filesystem on a partition separate from my main OS X system/boot >>>>> files. >>>>> >>>> Now >>>> >>>>> I just want to mount that partition from FreeBSD. Is this >>>>> possible? I >>>>> can >>>>> see the slice in /dev as ad5s3, but there's no partitions on >>>>> that slice >>>>> >>>> to >>>> >>>>> mount (ad5s3a, for example), nor am I familiar enough with ZFS >>>>> to know >>>>> >>>> what >>>> >>>>> it should look like from FreeBSD. I have tried 'mount -t zfs / >>>>> dev/ad5s3 >>>>> /media/temp' without success. zfs.ko is loaded (seen in kldstat) >>>>> and >>>>> >>>> gives >>>> >>>>> the usual message of it being experimental and being version >>>>> 6.0. In a >>>>> >>>> post >>>> >>>>> on the forums (http://forums.freebsd.org/showthread.php?t=1613) >>>>> it was >>>>> suggested that I try 'zpool list' but that returned 'no pools >>>>> available'. >>>>> >>>> I >>>> >>>>> tried 'zfs list' as well and got 'no datasets available'. >>>>> >>>>> My GUID partition table (OS X) and MBR (FreeBSD) are synced, so >>>>> they >>>>> both >>>>> show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris >>>>> Usr' on >>>>> >>>> the >>>> >>>>> GPT and type B4 iirc on the MBR). I used an EFI booting program >>>>> called >>>>> >>>> rEFIt >>>> >>>>> to sync the tables - could the MBR type of the slice be the >>>>> reason I >>>>> >>>> can't >>>> >>>>> mount it from FreeBSD? >>>>> >>>>> I've searched long and hard for any posts about using zfs as a >>>>> way to >>>>> >>>> share >>>> >>>>> a partition between any two OSs, but have not found any >>>>> references on >>>>> how >>>>> >>>> to >>>> >>>>> use a zfs slice as a shared data partition. Can it only be >>>>> mounted from >>>>> >>>> the >>>> >>>>> OS in which it was created? Any thoughts on what I might do here? >>>>> >>>>> >>>>> Thanks much, >>>>> John >>>>> >>>> >>>> I am sorry, I wanted to ask what >>>> >>>> zpool import >>>> >>>> returns. >>>> >>>> Regards, >>>> >>>> Boris Kotzev >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>> 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" >>> >>> > _______________________________________________ > 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 Wed Jan 21 06:40:33 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EC5B1065690; Wed, 21 Jan 2009 06:40:33 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 4ADA48FC29; Wed, 21 Jan 2009 06:40:33 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPWlK-000DZu-7o; Wed, 21 Jan 2009 16:40:32 +1000 Message-ID: <4976C370.4030406@dannysplace.net> Date: Wed, 21 Jan 2009 16:40:48 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Koen Smits References: <20081031033208.GA21220@icarus.home.lan> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2009-01-21 16:40:30 X-Connected-IP: 203.206.171.212:3036 X-Message-Linecount: 83 X-Body-Linecount: 68 X-Message-Size: 3048 X-Body-Size: 1958 X-Received-Count: 1 X-Recipient-Count: 4 X-Local-Recipient-Count: 4 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: kgysmits@gmail.com, koitsu@freebsd.org, freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=ALL_TRUSTED, AWL, DEAR_SOMETHING, TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 06:40:34 -0000 Koen Smits wrote: > Please let us know what Areca says about the caching. > If you ask me, these results definitely are cached. > Sorry for the delay. Areca got back to me. It took a few days but I got someone who seemed to know what they were talking about. >From what I can gather the cache is always on. You can configure it to be writeback or writethrough in some situations but when that is not an option, writethrough is the default. I could not get any information about read caching although I might send an email to see what happens. Here is the transcript of the conversation: Me: I have a rather simple question about the 1231 controller. Can you please explain the difference between using disks in JBOD mode and using disks in passthrough mode. I have a feeling that the controller uses it's onboard cache when in passthrough mode. Is this the case? Also, are both read and write operations cached? Areca Support: Dear Sir, the only difference is in JBOD mode, controller configure all drives as passthrough disk. in RAID mode, you have to configure passthrough disk by yourself in RAID mode in other words, you can use raid with passthrough disks at saem time in RAID mode but JBOD mode not. Me: So does that mean if I use passthrough, I am not protected by the cache/battery backup? I ask because there is an option for cache mode when creating a passthrough disk. i.e. Write-Back or Write-Through Areca Support: Dear Sir, in JBOD mode, the default setting writeback mode. with writeback mode, you will need a battery module to protect the data remain in cache in case you got a power failure problem. Me: And so in Passthrough mode I am still protected with the battery backup? So JBOD = WriteBack Cache with protection of the battery backup. Passthrough = WriteBack or WriteThrough also with protection of the battery backup. Is this correct? Areca Support: Dear Sir, if you have battery module attached, yes. From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 09:16:08 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEA231065698; Wed, 21 Jan 2009 09:16:08 +0000 (UTC) (envelope-from kgysmits@gmail.com) Received: from mail-fx0-f11.google.com (mail-fx0-f11.google.com [209.85.220.11]) by mx1.freebsd.org (Postfix) with ESMTP id 08A1B8FC16; Wed, 21 Jan 2009 09:16:07 +0000 (UTC) (envelope-from kgysmits@gmail.com) Received: by fxm4 with SMTP id 4so867902fxm.19 for ; Wed, 21 Jan 2009 01:16:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=yZ4uEtJCAnaEibAnFddhJ+v4r4kGXxmUCEPUXAM2mjA=; b=MoMPe0se1U50ovxCW4hNRWX/1+Ha0SU5Yc5ieSnIq2PAqkQuQA6oYcLoaWL2CF8JBn BaYX8z68gTYenmY2Yuy7pNqy88aUAjpHjaA8lcVKaahXcWnQaJ9nmojJBfE+W9GHSnYa M6oh0Ce0PMDvWul18x7N4teedsOqnZY8NUb9U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IZ8NTaaIRk8q4IFgiMPjBHxjyxc/Rl18c2ezu3OpGukSw3tUFOykLW76tfy5YJsF3r ROOMWApNuStqpi2S9hMxOuaZvnvElsoNBo97+picO5pgWSsYsZERnodStPT1WvXLM5M3 QXTBYqIYsiW/YRp6+HiCEYEqDNMgi2PxVTxr0= MIME-Version: 1.0 Received: by 10.223.110.3 with SMTP id l3mr3299522fap.48.1232529366886; Wed, 21 Jan 2009 01:16:06 -0800 (PST) In-Reply-To: <4976C370.4030406@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> <4976C370.4030406@dannysplace.net> Date: Wed, 21 Jan 2009 10:16:06 +0100 Message-ID: From: Koen Smits To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. 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, 21 Jan 2009 09:16:09 -0000 > > Areca Support: > Dear Sir, > the only difference is > in JBOD mode, controller configure all drives as passthrough disk. > in RAID mode, you have to configure passthrough disk by yourself in RAID > mode > > in other words, you can use raid with passthrough disks at saem time in > RAID mode but JBOD mode not. > > Me: > So does that mean if I use passthrough, I am not protected by the > cache/battery backup? I ask because there is an option for cache mode > when creating a passthrough disk. i.e. Write-Back or Write-Through missed my 'reply to all' button, here goes the 2nd try. So 'passthrough' means that the controller lets the OS see the physical disks just as they are, but with an invisible cache in between that buffers operations. This way there is no advantage of the onboard XOR engine, but you do profit from the intelligent cache, which is the most important anyway imho. JBOD mode is at a disadvantage because in this mode the OS sees one large drive, and is not able to stripe the data to multiple disks, not taking advantage of the fact that you have multple spindles available. Makes sense to me :). I must admit, I do like these results. Very promising. Further tests would be using an SSD for the ZIL, testing linux and NT, etc. But let's not go there ;). From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 13:15:19 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 490C61065850; Wed, 21 Jan 2009 13:15:19 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id EA1998FC3A; Wed, 21 Jan 2009 13:15:18 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPcvI-000MOa-EZ; Wed, 21 Jan 2009 23:15:18 +1000 Message-ID: <49771FEE.1070606@dannysplace.net> Date: Wed, 21 Jan 2009 23:15:26 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Koen Smits , freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org References: <20081031033208.GA21220@icarus.home.lan> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> <4976C370.4030406@dannysplace.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2009-01-21 23:15:13 X-Connected-IP: 203.206.171.212:3576 X-Message-Linecount: 65 X-Body-Linecount: 51 X-Message-Size: 3088 X-Body-Size: 2027 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: kgysmits@gmail.com, freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=ALL_TRUSTED, AWL, DEAR_SOMETHING, TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 13:15:20 -0000 Koen Smits wrote: > Areca Support: > Dear Sir, > the only difference is > in JBOD mode, controller configure all drives as passthrough disk. > in RAID mode, you have to configure passthrough disk by yourself in RAID > mode > > in other words, you can use raid with passthrough disks at saem time in > RAID mode but JBOD mode not. > > Me: > So does that mean if I use passthrough, I am not protected by the > cache/battery backup? I ask because there is an option for cache mode > when creating a passthrough disk. i.e. Write-Back or Write-Through > > > So 'passthrough' means that the controller lets the OS see the physical > disks just as they are, but with an invisible cache in between that > buffers operations. This way there is no advantage of the onboard XOR > engine, but you do profit from the intelligent cache, which is the most > important anyway imho. Not exactly. In JBOD mode ALL disks are passed through to the OS. You cannot have RAID. The cache is set to Write-Back. In RAID mode, you can mix raid5, raid6 and Passthrough (which are like JBOD but allow writethrough or writeback cache at your discretion). > JBOD mode is at a disadvantage because in this mode the OS sees one > large drive, and is not able to stripe the data to multiple disks, not > taking advantage of the fact that you have multple spindles available. > Makes sense to me :). No, in JBOD, the OS sees all disks individually. What you are talking about is a concatenated disk set which I don't think has a raid level. > I must admit, I do like these results. Very promising. Me too, although I am not sure if I like the idea of turning off the cache flushes in ZFS. I'd be a lot happier if the Areca card would tell me how 'full' the cache was. I'd also love to know if there was a way for the disk to tell me what the status if it's own cache is. > Further tests would be using an SSD for the ZIL, testing linux and NT, > etc. But let's not go there ;). Nope :-) -D From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 16:25:47 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 562FB1065670 for ; Wed, 21 Jan 2009 16:25:47 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 17BCB8FC23 for ; Wed, 21 Jan 2009 16:25:47 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 491EA6D43F; Wed, 21 Jan 2009 16:25:46 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 2D694844A1; Wed, 21 Jan 2009 17:25:46 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Andrew Brampton" References: Date: Wed, 21 Jan 2009 17:25:45 +0100 In-Reply-To: (Andrew Brampton's message of "Mon, 19 Jan 2009 01:01:36 +0000") Message-ID: <868wp4pqwm.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Pseudofs and pfs_attr_t for non-process based 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: Wed, 21 Jan 2009 16:25:47 -0000 "Andrew Brampton" writes: > Basically pn_attr calls my pfs_attr_t function pointer, but only if > the proc !=3D null. Now in my case none of my files are created > PFS_PROCDEP flag, which mean proc will always be null. So unless you > are writing a pseudofs which is dependent on the process calling it, > you cannot use a pfs_attr_t function pointer, meaning I can't change > the attributes on my pseudo files. > > Now, to fix this problem I made a very simple patch which will call > pn_attr regardless of proc being null or not. By doing this I had to > also make a minor change in procfs.c as it assumes a valid proc is > always passed in. Sounds sensible, but your patches are mangled. Could you please regenerate them using 'svn diff -x-p' on a non-Windows machine? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Wed Jan 21 17:37:45 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48CC91065670 for ; Wed, 21 Jan 2009 17:37:45 +0000 (UTC) (envelope-from brampton@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 C023B8FC19 for ; Wed, 21 Jan 2009 17:37:44 +0000 (UTC) (envelope-from brampton@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so544569nfh.33 for ; Wed, 21 Jan 2009 09:37:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=8oRem3pywwe2NdAXn8XuO6FLDulyfiam0kOxuWSoDC4=; b=cF8x+1hgAGods6vHCYOFSPoAkawyi/UljMT6vBbB4I7oDG9hVlcBgpsqoftd9lUg6x JPW0Seqij8qMQx8YagS9pyrN1thTPZYcCvbkQmlqv1nJCMJe4fM+ZItB71zGUs17XOz5 hEaYk6JaY9P+kh6ynTju9A5FoSYOVo1wWghOM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ViDI+50tiNCETLkTm7tCH4lo0X7jQW+faM4qObC9LvVLOFeHbcmDYaL4KEt+KuuU7O tVH7i4a5RO5igZErdDnfjt8clXR+tUCgRiDqCQW7tHeJBFNOIMekpxNl1C0VGfN+M+VM kEipEPt8/aHWrIOuPwbBGhD8b8pLyDW39crek= MIME-Version: 1.0 Sender: brampton@gmail.com Received: by 10.210.43.10 with SMTP id q10mr776793ebq.63.1232559463605; Wed, 21 Jan 2009 09:37:43 -0800 (PST) In-Reply-To: <868wp4pqwm.fsf@ds4.des.no> References: <868wp4pqwm.fsf@ds4.des.no> Date: Wed, 21 Jan 2009 17:37:43 +0000 X-Google-Sender-Auth: fa599733cc609cf2 Message-ID: From: Andrew Brampton To: freebsd-fs@freebsd.org, =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Content-Type: multipart/mixed; boundary=0015174c1146fe26ec0461019c59 Cc: Subject: Re: Pseudofs and pfs_attr_t for non-process based 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: Wed, 21 Jan 2009 17:37:45 -0000 --0015174c1146fe26ec0461019c59 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2009/1/21 Dag-Erling Sm=C3=B8rgrav : > Sounds sensible, but your patches are mangled. Could you please > regenerate them using 'svn diff -x-p' on a non-Windows machine? When you say mangled, did you just mean they had windows new lines? Regardless I've reattached the patches (with unix new lines), and using the -x-p command. I wasn't aware of -x-p but it looks useful. Enjoy Andrew --0015174c1146fe26ec0461019c59 Content-Type: application/octet-stream; name="pseudofs_vnops.patch" Content-Disposition: attachment; filename="pseudofs_vnops.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_fq8a1y6t0 SW5kZXg6IHN5cy9mcy9wc2V1ZG9mcy9wc2V1ZG9mc192bm9wcy5jCj09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHN5 cy9mcy9wc2V1ZG9mcy9wc2V1ZG9mc192bm9wcy5jCShyZXZpc2lvbiAxODc0MTUpCisrKyBzeXMv ZnMvcHNldWRvZnMvcHNldWRvZnNfdm5vcHMuYwkod29ya2luZyBjb3B5KQpAQCAtMjI2LDE0ICsy MjYsMTcgQEAgcGZzX2dldGF0dHIoc3RydWN0IHZvcF9nZXRhdHRyX2FyZ3MgKnZhKQogCWlmIChw cm9jICE9IE5VTEwpIHsKIAkJdmFwLT52YV91aWQgPSBwcm9jLT5wX3VjcmVkLT5jcl9ydWlkOwog CQl2YXAtPnZhX2dpZCA9IHByb2MtPnBfdWNyZWQtPmNyX3JnaWQ7Ci0JCWlmIChwbi0+cG5fYXR0 ciAhPSBOVUxMKQotCQkJZXJyb3IgPSBwbl9hdHRyKGN1cnRocmVhZCwgcHJvYywgcG4sIHZhcCk7 Ci0JCVBST0NfVU5MT0NLKHByb2MpOwogCX0gZWxzZSB7CiAJCXZhcC0+dmFfdWlkID0gMDsKIAkJ dmFwLT52YV9naWQgPSAwOwogCX0KIAorCWlmIChwbi0+cG5fYXR0ciAhPSBOVUxMKQorCQllcnJv ciA9IHBuX2F0dHIoY3VydGhyZWFkLCBwcm9jLCBwbiwgdmFwKTsKKworCWlmKHByb2MgIT0gTlVM TCkKKwkJUFJPQ19VTkxPQ0socHJvYyk7CisKIAlQRlNfUkVUVVJOIChlcnJvcik7CiB9CiAK --0015174c1146fe26ec0461019c59 Content-Type: application/octet-stream; name="procfs.patch" Content-Disposition: attachment; filename="procfs.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_fq8a29o31 SW5kZXg6IHN5cy9mcy9wcm9jZnMvcHJvY2ZzLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gc3lzL2ZzL3Byb2Nm cy9wcm9jZnMuYwkocmV2aXNpb24gMTg3NDE1KQorKysgc3lzL2ZzL3Byb2Nmcy9wcm9jZnMuYwko d29ya2luZyBjb3B5KQpAQCAtOTksNyArOTksNiBAQCBwcm9jZnNfZG9jdXJwcm9jKFBGU19GSUxM X0FSR1MpCiBpbnQKIHByb2Nmc19hdHRyKFBGU19BVFRSX0FSR1MpCiB7Ci0JUFJPQ19MT0NLX0FT U0VSVChwLCBNQV9PV05FRCk7CiAKIAkvKiBYWFggaW5lZmZpY2llbnQsIHNwbGl0IGludG8gc2Vw YXJhdGUgZnVuY3Rpb25zICovCiAJaWYgKHN0cmNtcChwbi0+cG5fbmFtZSwgImN0bCIpID09IDAg fHwKQEAgLTExMiwxMiArMTExLDE2IEBAIHByb2Nmc19hdHRyKFBGU19BVFRSX0FSR1MpCiAJICAg IHN0cmNtcChwbi0+cG5fbmFtZSwgImZwcmVncyIpID09IDApCiAJCXZhcC0+dmFfbW9kZSA9IDA2 MDA7CiAKLQlpZiAoKHAtPnBfZmxhZyAmIFBfU1VHSUQpICYmIHBuLT5wbl90eXBlICE9IHBmc3R5 cGVfcHJvY2RpcikKLQkJdmFwLT52YV9tb2RlID0gMDsKKwlpZiAocCAhPSBOVUxMKSB7CisJCVBS T0NfTE9DS19BU1NFUlQocCwgTUFfT1dORUQpOwogCi0JdmFwLT52YV91aWQgPSBwLT5wX3VjcmVk LT5jcl91aWQ7Ci0JdmFwLT52YV9naWQgPSBwLT5wX3VjcmVkLT5jcl9naWQ7CisJCWlmICgocC0+ cF9mbGFnICYgUF9TVUdJRCkgJiYgcG4tPnBuX3R5cGUgIT0gcGZzdHlwZV9wcm9jZGlyKQorCQkJ dmFwLT52YV9tb2RlID0gMDsKIAorCQl2YXAtPnZhX3VpZCA9IHAtPnBfdWNyZWQtPmNyX3VpZDsK KwkJdmFwLT52YV9naWQgPSBwLT5wX3VjcmVkLT5jcl9naWQ7CisJfQorCiAJcmV0dXJuICgwKTsK IH0KIAo= --0015174c1146fe26ec0461019c59-- From owner-freebsd-fs@FreeBSD.ORG Thu Jan 22 15:21:12 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F9E3106566C for ; Thu, 22 Jan 2009 15:21:12 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 30B3D8FC17 for ; Thu, 22 Jan 2009 15:21:12 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id EAF686D43F; Thu, 22 Jan 2009 15:21:10 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id D1060844C2; Thu, 22 Jan 2009 16:21:10 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Andrew Brampton References: <868wp4pqwm.fsf@ds4.des.no> Date: Thu, 22 Jan 2009 16:21:10 +0100 In-Reply-To: (Andrew Brampton's message of "Wed, 21 Jan 2009 17:37:43 +0000") Message-ID: <86iqo74ba1.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Pseudofs and pfs_attr_t for non-process based 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: Thu, 22 Jan 2009 15:21:12 -0000 Andrew Brampton writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Sounds sensible, but your patches are mangled. Could you please > > regenerate them using 'svn diff -x-p' on a non-Windows machine? > When you say mangled, did you just mean they had windows new lines? That, and incorrect indentation, which your new patches fixed. A tip: if your MUA allows it, set the MIME-type for patches to text/x-patch (or, as last resort, text/plain), otherwise they may get stripped by mailing list software and some corporate / institutional email gateways. In procfs_attr(), the vap->va_[ug]id assignments are redundant, since at this point pfs_getattr() has already done the exact same thing. The rest of the patch is fine, modulo style issues which already existed in my code. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Fri Jan 23 14:05:56 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB5491065672 for ; Fri, 23 Jan 2009 14:05:56 +0000 (UTC) (envelope-from brampton@gmail.com) Received: from mail-ew0-f20.google.com (mail-ew0-f20.google.com [209.85.219.20]) by mx1.freebsd.org (Postfix) with ESMTP id 16C8F8FC16 for ; Fri, 23 Jan 2009 14:05:55 +0000 (UTC) (envelope-from brampton@gmail.com) Received: by ewy13 with SMTP id 13so4276573ewy.19 for ; Fri, 23 Jan 2009 06:05:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=aJfhWeTbo6c+s5WNRM/OagDyQ0oiwKPjXrbkpRptDIo=; b=i5GGAXkR5zLbAJvXtO4YMvuFBBBz5Bk6YnhKMbX6fYo2VMpaqGnDcipuqPBK75INfI 1daLS/x8ebtndwg7S0JNXoUswUmZ+xLMvmZJGA7G0DK3QgrloYKJLw9B5fgXNY5zTXe9 vLcPD8iaIirckPuAXgTWFmBvkx2xxCD8LFwyM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=Cx49MNHoI1W+KPDYHGHGPlf83dTx2Dj3oUP3nSgsaAbuYoYC3Xexx08ckpHKro2TeL VoWfmx2Vc5iS9U3a4K/BWyzbrGBlnxjpBHpyRl76lG02zfD89VDFXh04fhehqMlR7iMD 23KRtXbErGxlO73t0S4N8M/cYQM8EKMOOSYh0= MIME-Version: 1.0 Sender: brampton@gmail.com Received: by 10.210.19.16 with SMTP id 16mr168262ebs.92.1232719555115; Fri, 23 Jan 2009 06:05:55 -0800 (PST) In-Reply-To: <86iqo74ba1.fsf@ds4.des.no> References: <868wp4pqwm.fsf@ds4.des.no> <86iqo74ba1.fsf@ds4.des.no> Date: Fri, 23 Jan 2009 14:05:55 +0000 X-Google-Sender-Auth: f4e8734a27393c14 Message-ID: From: Andrew Brampton To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , freebsd-fs Content-Type: multipart/mixed; boundary=000e0cd1e02830babb046126e3cb Cc: Subject: Re: Pseudofs and pfs_attr_t for non-process based 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: Fri, 23 Jan 2009 14:05:57 -0000 --000e0cd1e02830babb046126e3cb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2009/1/22 Dag-Erling Sm=C3=B8rgrav : > In procfs_attr(), the vap->va_[ug]id assignments are redundant, since at > this point pfs_getattr() has already done the exact same thing. The > rest of the patch is fine, modulo style issues which already existed in > my code. Here are both patches again, but only the procfs patch has changed. I have now removed the redundant code. thanks Andrew --000e0cd1e02830babb046126e3cb Content-Type: text/x-patch; charset=US-ASCII; name="pseudofs_vnops.patch" Content-Disposition: attachment; filename="pseudofs_vnops.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_fqaxdwxo0 SW5kZXg6IHN5cy9mcy9wc2V1ZG9mcy9wc2V1ZG9mc192bm9wcy5jCj09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHN5 cy9mcy9wc2V1ZG9mcy9wc2V1ZG9mc192bm9wcy5jCShyZXZpc2lvbiAxODc0MTUpCisrKyBzeXMv ZnMvcHNldWRvZnMvcHNldWRvZnNfdm5vcHMuYwkod29ya2luZyBjb3B5KQpAQCAtMjI2LDE0ICsy MjYsMTcgQEAgcGZzX2dldGF0dHIoc3RydWN0IHZvcF9nZXRhdHRyX2FyZ3MgKnZhKQogCWlmIChw cm9jICE9IE5VTEwpIHsKIAkJdmFwLT52YV91aWQgPSBwcm9jLT5wX3VjcmVkLT5jcl9ydWlkOwog CQl2YXAtPnZhX2dpZCA9IHByb2MtPnBfdWNyZWQtPmNyX3JnaWQ7Ci0JCWlmIChwbi0+cG5fYXR0 ciAhPSBOVUxMKQotCQkJZXJyb3IgPSBwbl9hdHRyKGN1cnRocmVhZCwgcHJvYywgcG4sIHZhcCk7 Ci0JCVBST0NfVU5MT0NLKHByb2MpOwogCX0gZWxzZSB7CiAJCXZhcC0+dmFfdWlkID0gMDsKIAkJ dmFwLT52YV9naWQgPSAwOwogCX0KIAorCWlmIChwbi0+cG5fYXR0ciAhPSBOVUxMKQorCQllcnJv ciA9IHBuX2F0dHIoY3VydGhyZWFkLCBwcm9jLCBwbiwgdmFwKTsKKworCWlmKHByb2MgIT0gTlVM TCkKKwkJUFJPQ19VTkxPQ0socHJvYyk7CisKIAlQRlNfUkVUVVJOIChlcnJvcik7CiB9CiAK --000e0cd1e02830babb046126e3cb Content-Type: text/x-patch; charset=US-ASCII; name="procfs.patch" Content-Disposition: attachment; filename="procfs.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_fqaxe4gq1 SW5kZXg6IHN5cy9mcy9wcm9jZnMvcHJvY2ZzLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gc3lzL2ZzL3Byb2Nm cy9wcm9jZnMuYwkocmV2aXNpb24gMTg3NDE1KQorKysgc3lzL2ZzL3Byb2Nmcy9wcm9jZnMuYwko d29ya2luZyBjb3B5KQpAQCAtOTksNyArOTksNiBAQCBwcm9jZnNfZG9jdXJwcm9jKFBGU19GSUxM X0FSR1MpCiBpbnQKIHByb2Nmc19hdHRyKFBGU19BVFRSX0FSR1MpCiB7Ci0JUFJPQ19MT0NLX0FT U0VSVChwLCBNQV9PV05FRCk7CiAKIAkvKiBYWFggaW5lZmZpY2llbnQsIHNwbGl0IGludG8gc2Vw YXJhdGUgZnVuY3Rpb25zICovCiAJaWYgKHN0cmNtcChwbi0+cG5fbmFtZSwgImN0bCIpID09IDAg fHwKQEAgLTExMiwxMSArMTExLDEyIEBAIHByb2Nmc19hdHRyKFBGU19BVFRSX0FSR1MpCiAJICAg IHN0cmNtcChwbi0+cG5fbmFtZSwgImZwcmVncyIpID09IDApCiAJCXZhcC0+dmFfbW9kZSA9IDA2 MDA7CiAKLQlpZiAoKHAtPnBfZmxhZyAmIFBfU1VHSUQpICYmIHBuLT5wbl90eXBlICE9IHBmc3R5 cGVfcHJvY2RpcikKLQkJdmFwLT52YV9tb2RlID0gMDsKKwlpZiAocCAhPSBOVUxMKSB7CisJCVBS T0NfTE9DS19BU1NFUlQocCwgTUFfT1dORUQpOwogCi0JdmFwLT52YV91aWQgPSBwLT5wX3VjcmVk LT5jcl91aWQ7Ci0JdmFwLT52YV9naWQgPSBwLT5wX3VjcmVkLT5jcl9naWQ7CisJCWlmICgocC0+ cF9mbGFnICYgUF9TVUdJRCkgJiYgcG4tPnBuX3R5cGUgIT0gcGZzdHlwZV9wcm9jZGlyKQorCQkJ dmFwLT52YV9tb2RlID0gMDsKKwl9CiAKIAlyZXR1cm4gKDApOwogfQo= --000e0cd1e02830babb046126e3cb--