From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 07:50: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 892FD106566B for ; Sun, 8 Feb 2009 07:50: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 6C1098FC0C for ; Sun, 8 Feb 2009 07:50: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 n187o3KS026626 for ; Sun, 8 Feb 2009 07:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n187o3kl026625; Sun, 8 Feb 2009 07:50:03 GMT (envelope-from gnats) Date: Sun, 8 Feb 2009 07:50:03 GMT Message-Id: <200902080750.n187o3kl026625@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Birgmeier Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Birgmeier List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2009 07:50:03 -0000 The following reply was made to PR kern/131360; it has been noted by GNATS. From: Martin Birgmeier To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load Date: Sun, 8 Feb 2009 08:40:31 +0100 (CET) Yet more info... here is output from top. Also, the following just happened: - I am editing this mail on the NFS server. - together with the top output from below, I was pasting a total of 1000 lines (my XTerm scroll size). - This caused the load on this server to effectively double again (over the pasted values shown below). Basically, I can only continue editing this mail if I suspend the build on the client machine, in which case the server immediately becomes responsive again. So maybe it is not a pppoa interaction with NFS serving, but any load on the server + NFS server makes the load on the server go to insane values. Or may be it is just additional TCP load, because I am displaying this XTerm on the NFS client (where the X server is running), and all the pasting has to go via the X server's TCP connection. Also, I have the impression that as long as only one of the 8 nfsd's on the server is busy, things are mostly normal, but as soon as more than one starts doing work (as seen in the output below), the load on the server goes way up. And regarding "mostly normal": even if only one nfsd seems to be active, the load on the server is already close to one - assuming that an nfsd does not do much more than network and disk i/o this really should not be the case (and was not under 6.3, where the load was low even under quite heavy NFS i/o). So maybe it is a ULE problem, after all? last pid: 2527; load averages: 14.71, 10.36, 6.13 up 0+01:04:43 08:21:08 111 processes: 9 running, 102 sleeping CPU: 1.4% user, 0.0% nice, 90.5% system, 8.1% interrupt, 0.0% idle Mem: 135M Active, 745M Inact, 119M Wired, 1012K Cache, 112M Buf, 248M Free Swap: 2048M Total, 2048M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 971 root 1 4 0 3128K 944K - 13:45 40.28% nfsd 972 root 1 4 0 3128K 944K - 2:19 15.09% nfsd 973 root 1 4 0 3128K 944K - 1:31 10.16% nfsd 974 root 1 4 0 3128K 944K - 1:03 6.05% nfsd 975 root 1 4 0 3128K 944K - 0:49 4.59% nfsd 977 root 1 4 0 3128K 944K - 0:41 3.56% nfsd 978 root 1 4 0 3128K 944K - 0:35 2.64% nfsd 976 root 1 4 0 3128K 944K - 0:31 1.81% nfsd 2527 root 1 96 0 3164K 992K RUN 0:00 1.54% rsh 1471 root 1 81 -15 5032K 2716K select 0:05 0.05% ppp 919 root 1 96 0 3128K 3148K select 2:16 0.00% amd 1539 root 1 96 0 6508K 4964K RUN 0:10 0.00% xterm 1140 squid 1 4 0 12000K 10152K sbwait 0:05 0.00% perl5.8.9 1130 squid 1 96 0 15660K 10820K RUN 0:05 0.00% squid 1141 squid 1 4 0 12000K 10148K sbwait 0:04 0.00% perl5.8.9 1142 squid 1 4 0 12000K 10148K sbwait 0:04 0.00% perl5.8.9 1143 squid 1 4 0 12000K 10104K sbwait 0:03 0.00% perl5.8.9 From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 08:10:06 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 ECA1D106566B for ; Sun, 8 Feb 2009 08:10:06 +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 C09BC8FC19 for ; Sun, 8 Feb 2009 08:10:06 +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 n188A6h3044399 for ; Sun, 8 Feb 2009 08:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n188A6oB044398; Sun, 8 Feb 2009 08:10:06 GMT (envelope-from gnats) Date: Sun, 8 Feb 2009 08:10:06 GMT Message-Id: <200902080810.n188A6oB044398@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Birgmeier Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Birgmeier List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2009 08:10:07 -0000 The following reply was made to PR kern/131360; it has been noted by GNATS. From: Martin Birgmeier To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load Date: Sun, 8 Feb 2009 09:00:20 +0100 (CET) Sorry for the many posts... this is problem is really nagging me, and I need to clarify an error I made: sysctl kern.sched.name on the server reports '4BSD', so it's not ULE as I wrote in my previous posting. From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 08: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 C53C3106566B for ; Sun, 8 Feb 2009 08: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 63A398FC08 for ; Sun, 8 Feb 2009 08: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 n188K30k052429 for ; Sun, 8 Feb 2009 08:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n188K3st052428; Sun, 8 Feb 2009 08:20:03 GMT (envelope-from gnats) Date: Sun, 8 Feb 2009 08:20:03 GMT Message-Id: <200902080820.n188K3st052428@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Birgmeier Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Birgmeier List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2009 08:20:05 -0000 The following reply was made to PR kern/131360; it has been noted by GNATS. From: Martin Birgmeier To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/131360: [nfs] poor scaling behavior of the NFS server under load Date: Sun, 8 Feb 2009 09:12:46 +0100 (CET) Another top snapshot on the server, scenario is the following: - make -j4 buildworld running on the client, currently in "===> kerberos5/lib/libkadm5srv (all)" - on the server, in addition to serving NFS, also running a 'svn log' command, where the repository is also served by the server via http (httpd, subversion repo, and svn log all running on the server, displaying in an XTerm running on the client). If I do the 'svn log' without NFS load from the client (buildworld stopped), there is nearly instantaneous output. If I do it with a running buildworld on the client, I get the a top output similar to the one below (actually, it is very hard to capture the "worst" moments, as the server is so unresponsive - in fact the load was something like 25, and each of the 8 nfsds consumed about 10% of CPU). last pid: 2527; load averages: 14.71, 10.36, 6.13 up 0+01:04:43 08:21:08 111 processes: 9 running, 102 sleeping CPU: 1.4% user, 0.0% nice, 90.5% system, 8.1% interrupt, 0.0% idle Mem: 135M Active, 745M Inact, 119M Wired, 1012K Cache, 112M Buf, 248M Free Swap: 2048M Total, 2048M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 971 root 1 4 0 3128K 944K - 13:45 40.28% nfsd 972 root 1 4 0 3128K 944K - 2:19 15.09% nfsd 973 root 1 4 0 3128K 944K - 1:31 10.16% nfsd 974 root 1 4 0 3128K 944K - 1:03 6.05% nfsd 975 root 1 4 0 3128K 944K - 0:49 4.59% nfsd 977 root 1 4 0 3128K 944K - 0:41 3.56% nfsd 978 root 1 4 0 3128K 944K - 0:35 2.64% nfsd 976 root 1 4 0 3128K 944K - 0:31 1.81% nfsd 2527 root 1 96 0 3164K 992K RUN 0:00 1.54% rsh 1471 root 1 81 -15 5032K 2716K select 0:05 0.05% ppp 919 root 1 96 0 3128K 3148K select 2:16 0.00% amd 1539 root 1 96 0 6508K 4964K RUN 0:10 0.00% xterm 1140 squid 1 4 0 12000K 10152K sbwait 0:05 0.00% perl5.8.9 1130 squid 1 96 0 15660K 10820K RUN 0:05 0.00% squid 1141 squid 1 4 0 12000K 10148K sbwait 0:04 0.00% perl5.8.9 1142 squid 1 4 0 12000K 10148K sbwait 0:04 0.00% perl5.8.9 1143 squid 1 4 0 12000K 10104K sbwait 0:03 0.00% perl5.8.9 From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 08:44:55 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 5887B106566B for ; Sun, 8 Feb 2009 08:44:55 +0000 (UTC) (envelope-from dan.cojocar@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.249]) by mx1.freebsd.org (Postfix) with ESMTP id 15ADA8FC17 for ; Sun, 8 Feb 2009 08:44:54 +0000 (UTC) (envelope-from dan.cojocar@gmail.com) Received: by an-out-0708.google.com with SMTP id b38so737283ana.13 for ; Sun, 08 Feb 2009 00:44:54 -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 :content-transfer-encoding; bh=ah//p8ueV5ADLyPhU5zw6CX9wEFjYa4gV4btqAe6NWo=; b=oC668MrD19cw+wi0XPrgBQbvmKoJ1PkzgCDWI8slYT1Dk6DBbiMKdnX3cjkZubNElg ZYihWx63jww69BDLUe1hYZtue8pC7gA8Khi5/qVtJSpw5lomoap9j08RKELqd4fRnCmo GRNf8xuQkxiuQDAgCq4aYuA3ywql1Nil61M9A= 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:content-transfer-encoding; b=Eo/vqE67v2PuEv7HXczIzyDiSuJffjlarLlZU5EA//R+dyNM2xWTHvwKlGRpDVma2a C0AzG0xJiU+RsNBNZccYGMpRBqLC6AYOIu12zUCfrQDVorAnOMNFW3RGb9hE4vNYMdl2 7pT5zJmoCx/lue2oXZ5JC6huFTQQENmEjzUjQ= MIME-Version: 1.0 Received: by 10.100.125.9 with SMTP id x9mr2146376anc.65.1234082694381; Sun, 08 Feb 2009 00:44:54 -0800 (PST) In-Reply-To: References: Date: Sun, 8 Feb 2009 10:44:54 +0200 Message-ID: From: Dan Cojocar To: Wesley Morgan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: zfs replace disk has failed 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, 08 Feb 2009 08:44:55 -0000 On Sun, Feb 8, 2009 at 12:04 AM, Wesley Morgan wrote: > On Tue, 3 Feb 2009, Dan Cojocar wrote: > >> Hello all, >> In a mirror(ad1,ad2) configuration one of my disk(ad1) had failed, >> after replacing the failed disk with a new one using: >> zpool replace tank ad1 >> I have noticed that the replace is taking too long and that the system >> is not responding, after restart the new disk was not recognized any >> more in bios :(, I have tested also in another box and the disk was >> not recognized there too. >> I have installed a new one on the same location (ad1 I think). Then >> the zpool status has reported something like this (this is from memory >> because I have made many changes back then, I don't remember exactly >> if the online disk was ad1 or ad2): >> >> zpool status >> pool: tank >> state: DEGRADED >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> tank DEGRADED 0 0 0 >> mirror DEGRADED 0 0 0 >> replacing UNAVAIL 0 387 0 >> insufficient replicas >> 10193841952954445329 REMOVED 0 0 0 was >> /dev/ad1/old >> 9318348042598806923 FAULTED 0 0 0 was /dev/ad1 >> ad2 ONLINE 0 0 0 >> At this stage I was thinking that if I will attach the new disk (ad1) >> to the mirror I will get sufficient replicas to detach >> 9318348042598806923 (this one was the disk that has failed the second >> time), so I did an attach, after the resilvering process has completed >> with success, I had: >> zpool status >> pool: tank >> state: DEGRADED >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> tank DEGRADED 0 0 0 >> mirror DEGRADED 0 0 0 >> replacing UNAVAIL 0 387 0 >> insufficient replicas >> 10193841952954445329 REMOVED 0 0 0 was >> /dev/ad1/old >> 9318348042598806923 FAULTED 0 0 0 was /dev/ad1 >> ad2 ONLINE 0 0 0 >> ad1 ONLINE 0 0 0 >> And I'm not able to detach 9318348042598806923 :(, and another bad >> news is that if I try to access something under /tank the operation is >> hanging, eg: if I do a ls /tank is freezing and if I do in another >> console: zpool status which was working before ls, now it's freezing >> too. >> What should I do next? >> Thanks, >> Dan > > ZFS seems to fall over on itself if a disk replacement is interrupted and > the replacement drive goes missing. > > By attaching the disk, you now have a 3-way mirror. The two possibilties for > you would be to roll the array back to a previous txg, which I'm not at all > sure would work, or to create a fake device the same size as the array > devices and put a label on it that emulates the missing device, and you can > then cancel the replacement. Once the replacement is cancelled, you should > be able to remove the nonexistent device. Note, that the labels are all > checksummed with sha256 so it's not a simple hex edit (unless you can > calculate checksums by hand also!). > > If you send me the first 512k of either ad1 or ad2 (off-list of course), I > can alter the labels to be the missing guids, and you can use md devices and > sparse files to fool zpool. > Hello Wesley, This was a production server so I had to restore the mirror from the backup. Can you explain a bit how can someone alter the labels of a disk in a pool? Thanks, Dan From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 13:28:11 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 529E9106566C; Sun, 8 Feb 2009 13:28:11 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 295318FC13; Sun, 8 Feb 2009 13:28:11 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (kib@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n18DSBwo088384; Sun, 8 Feb 2009 13:28:11 GMT (envelope-from kib@freefall.freebsd.org) Received: (from kib@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n18DSBhA088380; Sun, 8 Feb 2009 13:28:11 GMT (envelope-from kib) Date: Sun, 8 Feb 2009 13:28:11 GMT Message-Id: <200902081328.n18DSBhA088380@freefall.freebsd.org> To: kib@FreeBSD.org, freebsd-fs@FreeBSD.org, kib@FreeBSD.org From: kib@FreeBSD.org Cc: Subject: Re: kern/131356: [tmpfs][patch] unlink(2) on tmpfs removs wrong files with hard-links 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, 08 Feb 2009 13:28:11 -0000 Synopsis: [tmpfs][patch] unlink(2) on tmpfs removs wrong files with hard-links Responsible-Changed-From-To: freebsd-fs->kib Responsible-Changed-By: kib Responsible-Changed-When: Sun Feb 8 13:27:57 UTC 2009 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=131356 From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 14:13: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 412E61065672 for ; Sun, 8 Feb 2009 14:13:12 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id CFD788FC0A for ; Sun, 8 Feb 2009 14:13:11 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n18DbgGv010442 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sun, 8 Feb 2009 14:37:43 +0100 (CET) (envelope-from stb@lassitu.de) (authenticated as stb) Message-Id: <76873DDF-D21B-48AF-9AFB-5A2747BE406B@lassitu.de> From: Stefan Bethke To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 8 Feb 2009 14:37:42 +0100 X-Mailer: Apple Mail (2.930.3) Subject: zfs: using, then destroying a snapshot sometimes confuses zfs 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, 08 Feb 2009 14:13:12 -0000 Sorry I can't be more precise at the moment, but while creating a script that mirrors some zfs filesystems to another machine, I've now twice gotten weird behaviour and then a panic. The script iterates over a couple of zfs file systems: - creates a snapshot with zfs snapshot tank/foo@mirror - uses rsync to copy the contents of the snapshot with rsync /tank/ foo/.zfs/snapshot/mirror/ dest:... - destroys the snapshot with zfs destroy tank/foo@mirror During testing the script, I twice got to a point where, after the snapshot was created without an error message, rsync dropped out with an error message similar to "invalid file handle" on /tank/foo/.zfs/ snapshot. At that point, I could cd to /tank/foo/.zfs, but ls produced the same error message. I then tried to unmount the snapshot with zfs umount, and got a panic (which I also didn't manage to capture). Is this a generally known issue, or should I try to capture more information when this happens again? I'm running with these loader variables on amd64: vfs.zfs.arc_max="512M" vfs.zfs.prefetch_disable="1" vfs.zfs.zil_disable="1" Stefan -- Stefan Bethke Fon +49 151 14070811 From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 17:26: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 9226B106564A for ; Sun, 8 Feb 2009 17:26:09 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.121]) by mx1.freebsd.org (Postfix) with ESMTP id 52F368FC08 for ; Sun, 8 Feb 2009 17:26:09 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from shop.chemikals.org ([75.182.5.141]) by cdptpa-omta01.mail.rr.com with ESMTP id <20090208172608.DIAF6485.cdptpa-omta01.mail.rr.com@shop.chemikals.org>; Sun, 8 Feb 2009 17:26:08 +0000 Received: from localhost (morganw@localhost [127.0.0.1]) by shop.chemikals.org (8.14.3/8.14.3) with ESMTP id n18HQ7od027626; Sun, 8 Feb 2009 12:26:07 -0500 (EST) (envelope-from morganw@chemikals.org) Date: Sun, 8 Feb 2009 12:26:07 -0500 (EST) From: Wesley Morgan To: Dan Cojocar In-Reply-To: Message-ID: References: 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 Subject: Re: zfs replace disk has failed 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, 08 Feb 2009 17:26:10 -0000 On Sun, 8 Feb 2009, Dan Cojocar wrote: > On Sun, Feb 8, 2009 at 12:04 AM, Wesley Morgan wrote: >> On Tue, 3 Feb 2009, Dan Cojocar wrote: >> >>> Hello all, >>> In a mirror(ad1,ad2) configuration one of my disk(ad1) had failed, >>> after replacing the failed disk with a new one using: >>> zpool replace tank ad1 >>> I have noticed that the replace is taking too long and that the system >>> is not responding, after restart the new disk was not recognized any >>> more in bios :(, I have tested also in another box and the disk was >>> not recognized there too. >>> I have installed a new one on the same location (ad1 I think). Then >>> the zpool status has reported something like this (this is from memory >>> because I have made many changes back then, I don't remember exactly >>> if the online disk was ad1 or ad2): >>> >>> zpool status >>> pool: tank >>> state: DEGRADED >>> scrub: none requested >>> config: >>> >>> NAME STATE READ WRITE CKSUM >>> tank DEGRADED 0 0 0 >>> mirror DEGRADED 0 0 0 >>> replacing UNAVAIL 0 387 0 >>> insufficient replicas >>> 10193841952954445329 REMOVED 0 0 0 was >>> /dev/ad1/old >>> 9318348042598806923 FAULTED 0 0 0 was /dev/ad1 >>> ad2 ONLINE 0 0 0 >>> At this stage I was thinking that if I will attach the new disk (ad1) >>> to the mirror I will get sufficient replicas to detach >>> 9318348042598806923 (this one was the disk that has failed the second >>> time), so I did an attach, after the resilvering process has completed >>> with success, I had: >>> zpool status >>> pool: tank >>> state: DEGRADED >>> scrub: none requested >>> config: >>> >>> NAME STATE READ WRITE CKSUM >>> tank DEGRADED 0 0 0 >>> mirror DEGRADED 0 0 0 >>> replacing UNAVAIL 0 387 0 >>> insufficient replicas >>> 10193841952954445329 REMOVED 0 0 0 was >>> /dev/ad1/old >>> 9318348042598806923 FAULTED 0 0 0 was /dev/ad1 >>> ad2 ONLINE 0 0 0 >>> ad1 ONLINE 0 0 0 >>> And I'm not able to detach 9318348042598806923 :(, and another bad >>> news is that if I try to access something under /tank the operation is >>> hanging, eg: if I do a ls /tank is freezing and if I do in another >>> console: zpool status which was working before ls, now it's freezing >>> too. >>> What should I do next? >>> Thanks, >>> Dan >> >> ZFS seems to fall over on itself if a disk replacement is interrupted and >> the replacement drive goes missing. >> >> By attaching the disk, you now have a 3-way mirror. The two possibilties for >> you would be to roll the array back to a previous txg, which I'm not at all >> sure would work, or to create a fake device the same size as the array >> devices and put a label on it that emulates the missing device, and you can >> then cancel the replacement. Once the replacement is cancelled, you should >> be able to remove the nonexistent device. Note, that the labels are all >> checksummed with sha256 so it's not a simple hex edit (unless you can >> calculate checksums by hand also!). >> >> If you send me the first 512k of either ad1 or ad2 (off-list of course), I >> can alter the labels to be the missing guids, and you can use md devices and >> sparse files to fool zpool. >> > > Hello Wesley, > This was a production server so I had to restore the mirror from the backup. > Can you explain a bit how can someone alter the labels of a disk in a pool? > Thanks, > Dan > As far as I know there is no tool available to interactively edit a label, although since the source code that defines the labels and the data within is available it should be possible to write. For devices in the same pool, they should all have nearly identical labels, differing only in the actual guid for the device itself. In my situation, I simply altered the guid with a hex editor and borrowed the zfs sha256 code to write the correct checksum to the label and using gvirstor (md probably would have worked as well) was able to cancel the failed replacement. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 05:16:20 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 6873B106564A for ; Mon, 9 Feb 2009 05:16:20 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.freebsd.org (Postfix) with ESMTP id 29D658FC1A for ; Mon, 9 Feb 2009 05:16:19 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (localhost.your.org [127.0.0.1]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id B244C2AD6072 for ; Mon, 9 Feb 2009 04:59:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=dragondata.com; h= message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date; s=selector1; bh=FNZRv+VtLOXWhqPmNxyW iDR67pw=; b=oqHOpSDJHuS8xO+iOs2ZHax/J9HnrxWAHPPjdWJPo/l7Upukfdvs oPx5gGqIlinbzUD5trePm5i/x6VmrB53dS2rKgqAlV0QGUqGwiD0cR29jFgWvCNq E8DgrDQAUtVVccwvBgkKfYvQmbE9n96csSgA1RzD4QAMUuT3xKvroBY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=dragondata.com; h=message-id:from :to:content-type:content-transfer-encoding:mime-version:subject: date; q=dns; s=selector1; b=wfr+BWc54nZy/2M//P2cIKFvVGA1ap+71QHD qxNX3PfkBUJ6ez96/vowBNcCwhcx06uSvRFqfnjGfbPQcQWrxW+LtDFY6ktMsXXh 0IFPWrXRbtcs99wvMYCW71TCz9m4Vh/BNgTCe9cfyCya3UyyRXT/CS/FXn3NMxUz rnYUtxs= Received: from mail.your.org (server3-a.your.org [64.202.112.67]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by tokyo01.jp.mail.your.org (Postfix) with ESMTPS id 8844A2AD6069 for ; Mon, 9 Feb 2009 04:59:33 +0000 (UTC) Received: from pool011.dhcp.your.org (pool011.dhcp.your.org [69.31.99.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.your.org (Postfix) with ESMTPSA id 62AFBA0A414 for ; Mon, 9 Feb 2009 04:59:00 +0000 (UTC) Message-Id: <8E12CEFC-25DE-4B82-97BD-7ED717650089@dragondata.com> From: Kevin Day To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 8 Feb 2009 22:59:31 -0600 X-Mailer: Apple Mail (2.930.3) Subject: zio->io_cv deadlock 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, 09 Feb 2009 05:16:20 -0000 I'm playing with a -CURRENT install from a couple of weeks ago. Everything seems okay for a few days, then eventually every process ends up stuck in zio->io_cv. If I go to the console, it's responsive until I try logging in, then login is stuck in zio->io_cv as well. Ctrl-Alt-Esc drops me into ddb, but then ddb hangs instantly. Nothing on the console or syslog before it hangs. Anyone seen anything similar? -- Kevin Possibly relevant info: 8 core Opteron 64GB RAM da1 at twa0 bus 0 target 0 lun 1 da1: Fixed Direct Access SCSI-5 device da1: 100.000MB/s transfers da1: 4678158MB (9580867585 512 byte sectors: 255H 63S/T 596381C) server5# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT z 4.44T 1.19T 3.25T 26% ONLINE - server5# zpool status -v pool: z state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM z ONLINE 0 0 0 da1 ONLINE 0 0 0 errors: No known data errors server5# cat /boot/loader.conf vm.kmem_size_max="2048M" vm.kmem_size="2048M" vfs.zfs.arc_max="100M" zfs_load="YES" vfs.root.mountfrom="zfs:z" (tried lowering arc_max, didn't seem to help) From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 11:06:50 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 E2085106566B for ; Mon, 9 Feb 2009 11:06:50 +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 CF03D8FC08 for ; Mon, 9 Feb 2009 11:06:50 +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 n19B6ocA009098 for ; Mon, 9 Feb 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n19B6o7r009094 for freebsd-fs@FreeBSD.org; Mon, 9 Feb 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Feb 2009 11:06:50 GMT Message-Id: <200902091106.n19B6o7r009094@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, 09 Feb 2009 11:06:51 -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/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131353 fs gjournal kernel lock o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/131086 fs [ext2fs] mkfs.ext2 creates rotten partition o kern/131084 fs [xfs] xfs destroys itself after copying data o kern/131081 fs [zfs] User cannot delete a file when a ZFS dataset is o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file 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 o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po 42 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 13:40: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 BAF58106564A for ; Mon, 9 Feb 2009 13:40:09 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E35308FC17 for ; Mon, 9 Feb 2009 13:40:08 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA20655; Mon, 09 Feb 2009 15:21:54 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <49902DF2.8050206@icyb.net.ua> Date: Mon, 09 Feb 2009 15:21:54 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: FreeBSD Stable , freebsd-fs@FreeBSD.org References: <498AF8E1.7020206@icyb.net.ua> In-Reply-To: <498AF8E1.7020206@icyb.net.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: nfs umount soft hang 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, 09 Feb 2009 13:40:10 -0000 on 05/02/2009 16:34 Andriy Gapon said the following: > I have an NFS server and NFS client separated by a firewall. Both > servers are FreeBSD 7.1. > > Server configuration: > nfs_server_enable="YES" > nfs_server_flags="-t -n 4" > rpcbind_enable="YES" > mountd_flags="-r -p 737" > mountd_enable="YES" > > The firewall allows tcp and udp to port 111, but only tcp to ports 2049 > and 737 (configured for mountd, see above). > > On the client I use e.g. the following command for mounting: > mount -t nfs -o nfsv3,tcp,intr,rdirplus,-r=32768,-w=32768 > XXXX:/export/usr/obj /usr/obj > > Mounting and subsequent fs operations work flawlessly. > > When I unmount umount command hangs but can be interrupted with ^C. > Everything seems to be clean after that - the filesystem is unmounted, > there are no post-effects on both client and server. I think this is it: 377 /* 378 * Report to mountd-server which nfsname 379 * has been unmounted. 380 */ 381 if (ai != NULL && !(fflag & MNT_FORCE) && do_rpc) { 382 clp = clnt_create(hostp, RPCPROG_MNT, RPCMNT_VER1, "udp"); I wonder if umount could be smarter as to whether use udp or tcp here. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 15:55: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 DCC9C106567B for ; Mon, 9 Feb 2009 15:55:25 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from gw03.mail.saunalahti.fi (gw03.mail.saunalahti.fi [195.197.172.111]) by mx1.freebsd.org (Postfix) with ESMTP id 9DA388FC1B for ; Mon, 9 Feb 2009 15:55:25 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by gw03.mail.saunalahti.fi (Postfix) with SMTP id 62B132168FD; Mon, 9 Feb 2009 17:55:22 +0200 (EET) Date: Mon, 9 Feb 2009 17:55:21 +0200 From: Jaakko Heinonen To: Peter Jeremy Message-ID: <20090209155521.GA3418@a91-153-125-115.elisa-laajakaista.fi> References: <20090207200918.GA58657@test71.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090207200918.GA58657@test71.vk2pj.dyndns.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org Subject: Re: Unable to pwd in ZFS snapshot 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, 09 Feb 2009 15:55:26 -0000 Hi, On 2009-02-08, Peter Jeremy wrote: > I'm running -current from late last year (just after the ZFS v13 > import) and have found that I can't determine the current working > directory inside a snapshot: getcwd(3) first tries __getcwd() system call but it always fails because the VFS name cache is not supported for .zfs control directories. Secondly getcwd(3) tries to resolve working directory by traversing the directory tree to root but this fails too because the .zfs directory is normally hidden from the directory listing. (getcwd(3) uses readdir(3) to find component names) > This breaks (eg) make. I got around it by cloning the snapshot but > this behaviour strikes me as counter-intuitive (and the error message > leaves something to be desired). You can also work it around by making the ".zfs" directory visible: zfs set snapdir=visible volume -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 17:56:05 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 09E1B1065700 for ; Mon, 9 Feb 2009 17:56:04 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 481468FC2D for ; Mon, 9 Feb 2009 17:56:04 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id DDCA546B2C; Mon, 9 Feb 2009 12:56:03 -0500 (EST) Date: Mon, 9 Feb 2009 17:56:03 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jaakko Heinonen In-Reply-To: <20090209155521.GA3418@a91-153-125-115.elisa-laajakaista.fi> Message-ID: References: <20090207200918.GA58657@test71.vk2pj.dyndns.org> <20090209155521.GA3418@a91-153-125-115.elisa-laajakaista.fi> 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, Peter Jeremy Subject: Re: Unable to pwd in ZFS snapshot 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, 09 Feb 2009 17:56:17 -0000 On Mon, 9 Feb 2009, Jaakko Heinonen wrote: > On 2009-02-08, Peter Jeremy wrote: >> I'm running -current from late last year (just after the ZFS v13 import) >> and have found that I can't determine the current working directory inside >> a snapshot: > > getcwd(3) first tries __getcwd() system call but it always fails because the > VFS name cache is not supported for .zfs control directories. Secondly > getcwd(3) tries to resolve working directory by traversing the directory > tree to root but this fails too because the .zfs directory is normally > hidden from the directory listing. (getcwd(3) uses readdir(3) to find > component names) Now that we have a new VOP to assist in reverse-name resolution, it could be that ZFS could provide the back-end lookup to address this issue without forcing the use of the namecache for things we don't want to cache. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 07:10:13 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 F02C5106566C for ; Tue, 10 Feb 2009 07:10:13 +0000 (UTC) (envelope-from nbari@k9.cx) Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by mx1.freebsd.org (Postfix) with SMTP id 8423C8FC18 for ; Tue, 10 Feb 2009 07:10:13 +0000 (UTC) (envelope-from nbari@k9.cx) Received: from source ([74.125.44.28]) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKSZEoVdsdLmtleJgi8i3Og0/EV4pGzLv/@postini.com; Mon, 09 Feb 2009 23:10:13 PST Received: by yx-out-2324.google.com with SMTP id 8so162276yxb.29 for ; Mon, 09 Feb 2009 23:10:13 -0800 (PST) Received: by 10.65.40.16 with SMTP id s16mr3049741qbj.102.1234247897163; Mon, 09 Feb 2009 22:38:17 -0800 (PST) Received: from ?192.168.2.93? ([189.228.144.35]) by mx.google.com with ESMTPS id s35sm9335564qbs.6.2009.02.09.22.38.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 09 Feb 2009 22:38:16 -0800 (PST) Message-Id: <5EE9210C-B4C3-4579-BD33-A6C3CA392190@k9.cx> From: Nicolas de Bari Embriz Garcia Rojas To: freebsd-fs@freebsd.org Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-8-390138600" Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 10 Feb 2009 00:38:12 -0600 X-Pgp-Agent: GPGMail d55 (v55, Leopard) Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.930.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: GEOM: mfid1: corrupt or invalid GPT detected. GEOM: mfid1: GPT rejected -- may not be recoverable. 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, 10 Feb 2009 07:10:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-8-390138600 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit I have a dell poweredge 2900 III with a Dell PERC 6 Megaraid SAS driver Ver 3.00 On a raid1 (bootable) I have freebsd 7.1 latest stable version with default partion scheme and UFS, and on the raid5 I have a '/tank' partition made with ZFS The system works fine the only problem is that i keep geting this messages. GEOM: mfid1: corrupt or invalid GPT detected. GEOM: mfid1: GPT rejected -- may not be recoverable. Any idea on how to solve this or at least stop login that msg ? regards. --Apple-Mail-8-390138600 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkmRINQACgkQKHSHKa69I1sDdwCg0dOs3q0RXSL6DyEIPpUBJ3U7 OX4AoJxzX2CADLx6DvklffQ8c12DwJuP =ejkd -----END PGP SIGNATURE----- --Apple-Mail-8-390138600-- From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 16:52:10 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 1B675106566C for ; Tue, 10 Feb 2009 16:52:10 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi [195.197.172.115]) by mx1.freebsd.org (Postfix) with ESMTP id CB9A58FC08 for ; Tue, 10 Feb 2009 16:52:09 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by gw01.mail.saunalahti.fi (Postfix) with SMTP id 486D61519C6; Tue, 10 Feb 2009 18:52:05 +0200 (EET) Date: Tue, 10 Feb 2009 18:52:05 +0200 From: Jaakko Heinonen To: Robert Watson Message-ID: <20090210165204.GA4300@a91-153-125-115.elisa-laajakaista.fi> References: <20090207200918.GA58657@test71.vk2pj.dyndns.org> <20090209155521.GA3418@a91-153-125-115.elisa-laajakaista.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org, Peter Jeremy Subject: Re: Unable to pwd in ZFS snapshot 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, 10 Feb 2009 16:52:10 -0000 Hi, On 2009-02-09, Robert Watson wrote: > Now that we have a new VOP to assist in reverse-name resolution, it could be > that ZFS could provide the back-end lookup to address this issue without > forcing the use of the namecache for things we don't want to cache. I think that a bigger problem is how __getcwd() works. If single path component lookup fails from cache or with VOP_VPTOCNP __getwcd() will abort. So even if ZFS supported VOP_VPTOCNP perfectly some path components may be on a file system which doesn't and the hidden ".zfs" prevents userspace traversal from succeeding. Actually ZFS caches the hidden ".zfs" directory (but nothing below it). Thus if __getcwd() reverted to readdir scan only for those components which really require it getcwd(3) should work right now (as long as ".zfs" is in cache). Looks like someone has tried to do this already: http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027020.html The patch doesn't apply against head anymore. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 17:33:36 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 151FB106564A; Tue, 10 Feb 2009 17:33:36 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id A84DC8FC1D; Tue, 10 Feb 2009 17:33:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1LWwUH-0005Sx-LH; Tue, 10 Feb 2009 19:33:33 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n1AHXUhf026132 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 19:33:30 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n1AHXUll062458; Tue, 10 Feb 2009 19:33:30 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n1AHXTcV062457; Tue, 10 Feb 2009 19:33:29 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 10 Feb 2009 19:33:29 +0200 From: Kostik Belousov To: Jaakko Heinonen Message-ID: <20090210173329.GA62256@deviant.kiev.zoral.com.ua> References: <20090207200918.GA58657@test71.vk2pj.dyndns.org> <20090209155521.GA3418@a91-153-125-115.elisa-laajakaista.fi> <20090210165204.GA4300@a91-153-125-115.elisa-laajakaista.fi> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <20090210165204.GA4300@a91-153-125-115.elisa-laajakaista.fi> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1LWwUH-0005Sx-LH 9458849fa2284252e7f6f21358cfd59b X-Terabit: YES Cc: freebsd-fs@freebsd.org, Peter Jeremy , Robert Watson Subject: Re: Unable to pwd in ZFS snapshot 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, 10 Feb 2009 17:33:36 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 10, 2009 at 06:52:05PM +0200, Jaakko Heinonen wrote: >=20 > Hi, >=20 > On 2009-02-09, Robert Watson wrote: > > Now that we have a new VOP to assist in reverse-name resolution, it cou= ld be=20 > > that ZFS could provide the back-end lookup to address this issue withou= t=20 > > forcing the use of the namecache for things we don't want to cache. >=20 > I think that a bigger problem is how __getcwd() works. If single path > component lookup fails from cache or with VOP_VPTOCNP __getwcd() will > abort. So even if ZFS supported VOP_VPTOCNP perfectly some path > components may be on a file system which doesn't and the hidden ".zfs" > prevents userspace traversal from succeeding. >=20 > Actually ZFS caches the hidden ".zfs" directory (but nothing below it). > Thus if __getcwd() reverted to readdir scan only for those components > which really require it getcwd(3) should work right now (as long as > ".zfs" is in cache). >=20 > Looks like someone has tried to do this already: >=20 > http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027020.html >=20 > The patch doesn't apply against head anymore. It is being worked on right now. --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmRumkACgkQC3+MBN1Mb4hKawCfVwEd75djdbf6lbOn0adCDxRN Y4gAoOsS8xiXiA17ayoF5Oa2GaVpvaLE =PgRJ -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 18:35:17 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 120551065689; Tue, 10 Feb 2009 18:35:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 111E58FC16; Tue, 10 Feb 2009 18:35:14 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA14578; Tue, 10 Feb 2009 20:35:12 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4991C8DF.1020805@icyb.net.ua> Date: Tue, 10 Feb 2009 20:35:11 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: [repost] multiple filesystems sharing/clobbering device vnode 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, 10 Feb 2009 18:35:18 -0000 Unfortunately I wasn't able to devote enough time/thinking to this issue, so I am cowardly resorting to just reminding about it. -------- Original Message -------- Subject: multiple filesystems sharing/clobbering device vnode Date: Sat, 01 Mar 2008 11:33:37 +0200 From: Andriy Gapon To: freebsd-arch@freebsd.org First, a little demonstration suggested by Bruce Evance: [I hope you will continue reading after reboot] 1. mount_cd9660 /dev/acd0 /mnt1 2. mount -r /dev/acd0 /mnt2 # -r is important 3. ls -l /mnt1 The issue can be laconically described as follows: 1. We do not disallow multiple RO mounts of the same device (which could be done either on purpose or by an accident). 2. All popular (on-disk) filesystems use/clobber bufobj of device's vnode, even for RO mounts; some (ufs) do that even if mount fails. 3. There are no considerations for such a shared access, all filesystems act as if it is an exclusive owner of the vnode / its bufobj. Small snippet of code that speaks for itself (the most interesting lines are marked with XXX at the beginning): int g_vfs_open(struct vnode *vp, struct g_consumer **cpp, const char *fsname, int wr) { struct g_geom *gp; struct g_provider *pp; struct g_consumer *cp; struct bufobj *bo; int vfslocked; int error; g_topology_assert(); *cpp = NULL; pp = g_dev_getprovider(vp->v_rdev); if (pp == NULL) return (ENOENT); gp = g_new_geomf(&g_vfs_class, "%s.%s", fsname, pp->name); cp = g_new_consumer(gp); g_attach(cp, pp); error = g_access(cp, 1, wr, 1); if (error) { g_wither_geom(gp, ENXIO); return (error); } vfslocked = VFS_LOCK_GIANT(vp->v_mount); vnode_create_vobject(vp, pp->mediasize, curthread); VFS_UNLOCK_GIANT(vfslocked); *cpp = cp; XXX bo = &vp->v_bufobj; XXX bo->bo_ops = g_vfs_bufops; XXX bo->bo_private = cp; XXX bo->bo_bsize = pp->sectorsize; gp->softc = bo; return (error); } In addition to this, some filesystems (ufs) directly modify v_bufobj. I've been pondering this issue for over a month now, I have some ideas but they all are wanting in one aspect or other. I would like to hear ideas and opinions of the people on this list. P.S. for those who didn't actually run the test, here's a hand-copied excerpt from stack trace: g_io_request g_vfs_strategy ffs_geom_strategy cd9660_strategy VOP_STRATEGY_APV bufstrategy breadn bread cd9660_readdir -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed Feb 11 06:59: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 B6FBE1065673 for ; Wed, 11 Feb 2009 06:59:45 +0000 (UTC) (envelope-from dan.cojocar@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by mx1.freebsd.org (Postfix) with ESMTP id 7454D8FC13 for ; Wed, 11 Feb 2009 06:59:45 +0000 (UTC) (envelope-from dan.cojocar@gmail.com) Received: by an-out-0708.google.com with SMTP id b38so46723ana.13 for ; Tue, 10 Feb 2009 22:59:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=YHIjBdU2XDmYHfvOt6srXV4ROEc5YK5eC7sKznks/GY=; b=yDCAXgT3owa/WRQTazsjqPxGTOcOIZfnyBNzW8JN1nyqZm2F3C43M4NYNwaNC2E/Zl 7OOVzB5uUihGiYprLh2GUwmdDFrwSeMoZ1JheZRtzrM8N99Wqnqc6JzBqSpbxZ4Yj/rT jF1UFAtX3dMoY2ZzAJYzAuZ2fNDX4UuB/eLec= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=DSjRPONSX99oMr6nSnfGFeuXFX7Jnc1KEtAimMI5dHjq59qBKpZLuuiGZoA3pB+8lc jTkG7ccKhWVaRRllTd1CRBOa0MCAI4uZLJZdTp3ufWAFxgQoBbFyrDKjTVeRBnrdb2rq h6fKXgGJSwLS1ncBNDZYKQM57lKUkV9JsSHwk= MIME-Version: 1.0 Received: by 10.100.3.13 with SMTP id 13mr443447anc.37.1234335584676; Tue, 10 Feb 2009 22:59:44 -0800 (PST) Date: Wed, 11 Feb 2009 08:59:44 +0200 Message-ID: From: Dan Cojocar To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: zfs page fault 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, 11 Feb 2009 06:59:46 -0000 Hello, I have found this morning that one of my systems was not responding. After attaching a monitor I have found that the system has encountered a page fault. Here is the bt: Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x4c fault code =3D supervisor write, protection violation instruction pointer =3D 0x20:0x8051ba96 stack pointer =3D 0x28:0x83a8db7c frame pointer =3D 0x28:0x83a8db94 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 18 (vnlru) Physical memory: 1015 MB Dumping 273 MB: 258 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2 #0 doadump () at pcpu.h:246 246 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); (kgdb) bt #0 doadump () at pcpu.h:246 #1 0x80477e99 in db_fncall (dummy1=3D-2086086336, dummy2=3D0, dummy3=3D-2139548352, dummy4=3D0x83a8d920 "=C3yI\200\200=C8=C4\203") at /usr/src/sys/ddb/db_command.c:548 #2 0x80478291 in db_command (last_cmdp=3D0x8073531c, cmd_table=3D0x0, dopager=3D1) at /usr/src/sys/ddb/db_command.c:445 #3 0x804783ea in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #4 0x8047a23c in db_trap (type=3D12, code=3D0) at /usr/src/sys/ddb/db_main= .c:229 #5 0x8053df03 in kdb_trap (type=3D12, code=3D0, tf=3D0x83a8db3c) at /usr/src/sys/kern/subr_kdb.c:534 #6 0x806a804f in trap_fatal (frame=3D0x83a8db3c, eva=3D76) at /usr/src/sys/i386/i386/trap.c:920 #7 0x806a8310 in trap_pfault (frame=3D0x83a8db3c, usermode=3D0, eva=3D76) at /usr/src/sys/i386/i386/trap.c:842 #8 0x806a8ce5 in trap (frame=3D0x83a8db3c) at /usr/src/sys/i386/i386/trap.= c:522 #9 0x8069062b in calltrap () at /usr/src/sys/i386/i386/exception.s:165 #10 0x8051ba96 in _sx_xlock (sx=3D0x3c, opts=3D0, file=3D0x80969370 "/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/= dbuf.c", line=3D1807) at atomic.h:153 #11 0x80899235 in dmu_buf_update_user () from /boot/kernel/zfs.ko #12 0x808f0a53 in zfs_znode_dmu_fini () from /boot/kernel/zfs.ko #13 0x809136d6 in zfs_freebsd_reclaim () from /boot/kernel/zfs.ko #14 0x806b3132 in VOP_RECLAIM_APV (vop=3D0x80975580, a=3D0x83a8dc30) at vnode_if.c:1619 #15 0x80591b22 in vgonel (vp=3D0x874c4d9c) at vnode_if.h:830 #16 0x80596f13 in vnlru_free (count=3D245) at /usr/src/sys/kern/vfs_subr.c:= 899 #17 0x8059759e in vnlru_proc () at /usr/src/sys/kern/vfs_subr.c:768 #18 0x804f0f4f in fork_exit (callout=3D0x80597500 , arg=3D0x0, frame=3D0x83a8dd38) at /usr/src/sys/kern/kern_fork.c:821 #19 0x806906a0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:= 270 (kgdb) If someone needs more details I'm here. Thanks, Dan From owner-freebsd-fs@FreeBSD.ORG Wed Feb 11 18:07:52 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 72AF41065670 for ; Wed, 11 Feb 2009 18:07:52 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail36.syd.optusnet.com.au (mail36.syd.optusnet.com.au [211.29.133.76]) by mx1.freebsd.org (Postfix) with ESMTP id 00E3E8FC29 for ; Wed, 11 Feb 2009 18:07:51 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail36.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n1BI7ids020389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Feb 2009 05:07:45 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n1BI7h2h004665; Thu, 12 Feb 2009 05:07:43 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n1BI7h3j004664; Thu, 12 Feb 2009 05:07:43 +1100 (EST) (envelope-from peter) Date: Thu, 12 Feb 2009 05:07:43 +1100 From: Peter Jeremy To: Kevin Day Message-ID: <20090211180743.GC1467@server.vk2pj.dyndns.org> References: <8E12CEFC-25DE-4B82-97BD-7ED717650089@dragondata.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lc9FT7cWel8HagAv" Content-Disposition: inline In-Reply-To: <8E12CEFC-25DE-4B82-97BD-7ED717650089@dragondata.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org Subject: Re: zio->io_cv deadlock 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, 11 Feb 2009 18:07:53 -0000 --lc9FT7cWel8HagAv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Feb-08 22:59:31 -0600, Kevin Day wrote: > > I'm playing with a -CURRENT install from a couple of weeks ago. Everythin= g=20 > seems okay for a few days, then eventually every process ends up stuck in= =20 > zio->io_cv. If I go to the console, it's responsive until I try logging i= n,=20 > then login is stuck in zio->io_cv as well. Ctrl-Alt-Esc drops me into ddb= ,=20 > but then ddb hangs instantly. I think I've seen this as well, though I can't be sure because X.org 7.4 had trashed my console output. Definitely, I could enter DDB but the crashdump I requested (blind) never appeared. I don't believe I was doing anything unusual (other than trying to use X.org 7.4). --=20 Peter Jeremy --lc9FT7cWel8HagAv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmTE+8ACgkQ/opHv/APuIckhACgh4bVLa3V6bOQRXIDq/CNt7tQ /GoAoIJYJVKfIffZjp8OdxTCvjvXG9+M =flyT -----END PGP SIGNATURE----- --lc9FT7cWel8HagAv-- From owner-freebsd-fs@FreeBSD.ORG Thu Feb 12 10:25:28 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 450C8106566C for ; Thu, 12 Feb 2009 10:25:28 +0000 (UTC) (envelope-from glz@hidden-powers.com) Received: from mail.hidden-powers.com (mail.hidden-powers.com [213.242.135.162]) by mx1.freebsd.org (Postfix) with ESMTP id E55278FC1E for ; Thu, 12 Feb 2009 10:25:27 +0000 (UTC) (envelope-from glz@hidden-powers.com) Received: from mail.hidden-powers.com (localhost [127.0.0.1]) by dkim.hidden-powers.com (Postfix) with ESMTP id E9E9C6DFFF; Thu, 12 Feb 2009 11:06:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hidden-powers.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s= selector1; bh=qbUXouYizmVs3y+mr5vuvD5RfhE=; b=nXVSLLPNNjZRaVrLnU y0owwSriWYE7RV6oB3Tnu1KOxJe7KeUVj42LCB8uaPbASDxGxl1tnRM6ejT/Q7Wq LFCxHR+7QYo1BdayDrsDKdc4/h+Im7pvrVl2TN+yq79Oe/TvrUIIw6f21klLeNqX MvOujVJeb/45qKJkvNminXWSE= Received: from [172.16.2.110] (gw01.ismobile.com [212.73.186.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.hidden-powers.com (Postfix) with ESMTPSA id 7CE2D6DFFE; Thu, 12 Feb 2009 11:06:25 +0100 (CET) Date: Thu, 12 Feb 2009 11:06:25 +0100 From: Goran Lowkrantz To: Peter Jeremy , Kevin Day Message-ID: In-Reply-To: <20090211180743.GC1467@server.vk2pj.dyndns.org> References: <8E12CEFC-25DE-4B82-97BD-7ED717650089@dragondata.com> <20090211180743.GC1467@server.vk2pj.dyndns.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-fs@freebsd.org Subject: Re: zio->io_cv deadlock 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, 12 Feb 2009 10:25:28 -0000 --On February 12, 2009 5:07:43 +1100 Peter Jeremy wrote: > On 2009-Feb-08 22:59:31 -0600, Kevin Day wrote: >> >> I'm playing with a -CURRENT install from a couple of weeks ago. >> Everything seems okay for a few days, then eventually every process >> ends up stuck in zio->io_cv. If I go to the console, it's responsive >> until I try logging in, then login is stuck in zio->io_cv as well. >> Ctrl-Alt-Esc drops me into ddb, but then ddb hangs instantly. > > I think I've seen this as well, though I can't be sure because X.org 7.4 > had trashed my console output. Definitely, I could enter DDB but the > crashdump I requested (blind) never appeared. I don't believe I was > doing anything unusual (other than trying to use X.org 7.4). > I see this now and then in single-user mode during make installworld, ezjail-admin update -i or in multi-user when building a system in the background and updating ports at the same time. I have an USB keyboard and have not been able to break into the debugger with that, have legacy mode enabled in the bios (award). Anyone know how to send break from USB tgb? /glz From owner-freebsd-fs@FreeBSD.ORG Fri Feb 13 08:39:11 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 85048106566C; Fri, 13 Feb 2009 08:39:11 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 26E4F8FC12; Fri, 13 Feb 2009 08:39:11 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 4B79428448; Fri, 13 Feb 2009 16:39:10 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id CF14BEC6FC4; Fri, 13 Feb 2009 16:39:09 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id gI-PuKHIm9VU; Fri, 13 Feb 2009 16:39:04 +0800 (CST) Received: from charlie.delphij.net (c-69-181-141-49.hsd1.ca.comcast.net [69.181.141.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 6728EEC6FA0; Fri, 13 Feb 2009 16:39:02 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=BylQqQC07y4h0s4FsHUYNijoEOcPlDYRfRSE0sfzCi7d3oi8JK4lZPt3r7YEBVxZ/ BDDfrRKKZA9iZ1IgP8B1A== Message-ID: <499531A4.3020308@delphij.net> Date: Fri, 13 Feb 2009 00:39:00 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090202) MIME-Version: 1.0 To: Yoshihiro Ota References: <98869b7c0902100112s6dae54bm4c14487076ceb75c@mail.gmail.com> <20090212183440.GA1446@tops> <20090213001350.52470f39.ota@j.email.ne.jp> In-Reply-To: <20090213001350.52470f39.ota@j.email.ne.jp> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Gleb Kurtsou , freebsd-current@freebsd.org, imura@FreeBSD.org, =?UTF-8?B?6KO05Zu95YW0?= Subject: Re: patch: let msdosfs(vfat)/ntfs to support UTF-8 locale well X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2009 08:39:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (cc'ed to freebsd-fs@) I think it's important that someone familiar with the code review and evaluate the current patches and commit it against -HEAD... MSDOSFS patch (against 7.1): http://btload.googlegroups.com/web/msdosfs.patch?gda=MzIscT8AAABs_gmy4a1S9lRiXjEy-V5OpwtI67JnIGlz0zr18tjObOtoi5oIt3BJMRGeqGBbbj-ccyFKn-rNKC-d1pM_IdV0 NTFS patch: http://btload.googlegroups.com/web/ntfs.patch?gda=OqsHoDwAAABs_gmy4a1S9lRiXjEy-V5O7RN7t-m4MjZ-5dQn_EvaqDVCWO9_HyYEQJyRQYPtRCL9Wm-ajmzVoAFUlE7c_fAt Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEUEARECAAYFAkmVMaQACgkQi+vbBBjt66DN+wCghJbOUO7IfEwt5gFOB01uAAe1 NLwAmOQXPJsB+lT7o5MMk16Ck6eUJrQ= =ZGMA -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Sat Feb 14 12:53:49 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 BA1001065673 for ; Sat, 14 Feb 2009 12:53:49 +0000 (UTC) (envelope-from scjamorim@bsd.com.br) Received: from mail-qy0-f12.google.com (mail-qy0-f12.google.com [209.85.221.12]) by mx1.freebsd.org (Postfix) with ESMTP id 81D528FC1B for ; Sat, 14 Feb 2009 12:53:49 +0000 (UTC) (envelope-from scjamorim@bsd.com.br) Received: by qyk5 with SMTP id 5so1193469qyk.19 for ; Sat, 14 Feb 2009 04:53:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.97.194 with SMTP id m2mr1028702qcn.21.1234614645062; Sat, 14 Feb 2009 04:30:45 -0800 (PST) Date: Sat, 14 Feb 2009 10:30:45 -0200 Message-ID: <5859850b0902140430r585bf77fn6d70c3ce79a0c439@mail.gmail.com> From: =?ISO-8859-1?Q?Sylvio_C=E9sar_Teixeira_Amorim?= 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 Subject: Pendrive 8G+CAM_REQ_CMP_ERR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2009 12:53:50 -0000 Hello everyone, Gentlemen, I wonder if someone passed by the following problem, I have 3 Pendrive, 2 are 1, 1G and 8G, I'm using FreeBSD-7.1-stable, the problem is when you connect to 8G, the fbsd detects the device, da0, etc, but not create the / dev/da0 takes us about 10min trying to create this device, only appears after / dev/da0 and various error messages such as: IOERROR, CAM_REQ_CMP_ERR and not mounted. The 8G are of FAT32 and to recognize and are usually mounted in Linux, usually the mount of 1G in FreeBSD, but the filesystem is FAT16. Someone went through this problem? -- -=-=-=-=-=-=-=- Live free or die - UNIX* -=-=-=-=-=-=-= From owner-freebsd-fs@FreeBSD.ORG Sat Feb 14 19:29:20 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 ED35E106564A for ; Sat, 14 Feb 2009 19:29:19 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by mx1.freebsd.org (Postfix) with ESMTP id 908638FC0A for ; Sat, 14 Feb 2009 19:29:19 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by gxk24 with SMTP id 24so2296335gxk.19 for ; Sat, 14 Feb 2009 11:29:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=WmWK55j3cuqx+gO0TtNPy07rYRbqlXkJBL9yD+PgpzM=; b=sLh3aWJWu/0IQGbLYJtjrtNcix12iEKyfaTLICVVNWJkFZ6b4mhAujo0DgolIaoAzx 162gM57txLAUqYXQ/vzcKF4G9gIEMj81og5rlHiAeMOavc8LWFCsfC7MPlhDcbOGD+YA Hoc0nLRmmYMy9klxJPoyrSyg7Mo5sQ5nQ+BrE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=IqpsjYQikh6ehsX3Z1DlE+QHicCTm3HiAOTeS9gHng4iJTBVOqIH3UxdIZjnvMCXle Yfmn0hckiPP0CLB64WjaZ+4NsXAjUpSTqL6p+zm914eImBfge5zPhFQjjLG782X/wrIW koZD72d+sXwIuIYlOrb9ukke3P//nFb7MOFN8= MIME-Version: 1.0 Received: by 10.151.149.6 with SMTP id b6mr1486081ybo.122.1234638023079; Sat, 14 Feb 2009 11:00:23 -0800 (PST) Date: Sat, 14 Feb 2009 14:00:23 -0500 Message-ID: <5f67a8c40902141100w406b0a73h7cf487369e15ec8f@mail.gmail.com> From: Zaphod Beeblebrox To: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: When does the pool get bigger? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2009 19:29:20 -0000 I have a ZFS raid-Z array (FreeBSD-7.1p2) that I use for storing backups and media. I'm keenly awaiting the MFC of the ZFS v13 code, but I'm not in a hurry to run -CURRENT on this box. Anyways... The array was 5x 750G drives and I decided to upgrade to 5x 1.5T drives. I removed one 750G drive and inserted a 1.5T drive each time. All 5 are done resilvering now. When does the pool get bigger? The resilver of the last drive has finished, but the pool still reads [1:20:320]root@virtual:/usr/local/etc> zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT vr2 3.41T 3.16T 251G 92% ONLINE - ... which is the size with 750G drives. From owner-freebsd-fs@FreeBSD.ORG Sat Feb 14 20:58:29 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 BD35C1065710; Sat, 14 Feb 2009 20:58:29 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 425928FC1A; Sat, 14 Feb 2009 20:58:29 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id n1EKdNHr078343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 14 Feb 2009 21:39:23 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id n1EKdKQa080294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Feb 2009 21:39:20 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id n1EKdKX6083533; Sat, 14 Feb 2009 21:39:20 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id n1EKdKIl083532; Sat, 14 Feb 2009 21:39:20 +0100 (CET) (envelope-from ticso) Date: Sat, 14 Feb 2009 21:39:20 +0100 From: Bernd Walter To: Zaphod Beeblebrox Message-ID: <20090214203919.GV84964@cicely7.cicely.de> References: <5f67a8c40902141100w406b0a73h7cf487369e15ec8f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5f67a8c40902141100w406b0a73h7cf487369e15ec8f@mail.gmail.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.050, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: When does the pool get bigger? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2009 20:58:30 -0000 On Sat, Feb 14, 2009 at 02:00:23PM -0500, Zaphod Beeblebrox wrote: > I have a ZFS raid-Z array (FreeBSD-7.1p2) that I use for storing backups and > media. I'm keenly awaiting the MFC of the ZFS v13 code, but I'm not in a > hurry to run -CURRENT on this box. > > Anyways... The array was 5x 750G drives and I decided to upgrade to 5x 1.5T > drives. I removed one 750G drive and inserted a 1.5T drive each time. All > 5 are done resilvering now. > > When does the pool get bigger? The resilver of the last drive has finished, > but the pool still reads > > [1:20:320]root@virtual:/usr/local/etc> zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > vr2 3.41T 3.16T 251G 92% ONLINE - > > ... which is the size with 750G drives. You need to export/import the pool once. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.