From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 20:20:27 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19A7B7ED for ; Sun, 8 Feb 2015 20:20:27 +0000 (UTC) Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D4B9460E for ; Sun, 8 Feb 2015 20:20:26 +0000 (UTC) Received: by iery20 with SMTP id y20so3765829ier.9 for ; Sun, 08 Feb 2015 12:20:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=tvV7Hihys1hjN7tyRpG9hVI/yYZG3meqiA8kN/z4Baw=; b=PqHsn1/iZGsqlINCyv6m7xD992/LPgGpgg8UUv6iVBVYPh/8o0RL/EIA4FcejPKW8e 60rciTw9fTCev40+ikRbJmLuKamJENQCf8y6w2mKFr/bocMeJy9ZnmvYhVxa0vMND6dQ tT28qYrIbh82Dx3R/oMZX/5m1Sj6BPtGCWLNrI6psxPnyko5e6tGzc4h1KP5z0qE8+d7 G6FyZ9BfnPkKF2FpHn4guHvwna3gy8GhFgcM+ptJnquKRyLNA5J8qsZV9wjj/6J2XSAJ OFhyu375V+lgSBKFgk/ou4mJpnQ8P7SfrZBw3AK/o0eKc5005hqWT+DEj4RnmT9Fl3Hg WLkA== X-Gm-Message-State: ALoCoQkqmNq6U0FH0mP21LBN8sABrE3U9eMixcfHBEVFeVFxsCucyxDm/Tvg/k0j5pFEaxSBNNvd X-Received: by 10.50.79.163 with SMTP id k3mr13337757igx.30.1423426820327; Sun, 08 Feb 2015 12:20:20 -0800 (PST) Received: from sol.firepipe.net ([2601:1:adc0:2c1:7271:bcff:fe83:9550]) by mx.google.com with ESMTPSA id hg18sm4354050igb.1.2015.02.08.12.20.19 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Feb 2015 12:20:19 -0800 (PST) Sender: Will Andrews Date: Sun, 8 Feb 2015 13:20:17 -0700 From: Will Andrews To: Michelle Sullivan Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... Message-ID: <20150208202016.GA45601@sol.firepipe.net> References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline In-Reply-To: <54D4A552.7050502@sorbs.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2015 20:20:27 -0000 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 06, 2015 at 12:28:18PM +0100, Michelle Sullivan wrote: > root@colossus:~ # zdb -AAA -L -u -e storage > Segmentation fault (core dumped) [...] Getting stack traces from these zdb crash dumps can give a strong clue as to where the problem is. zdb turns on ASSERTs that are turned off by default in non-ZFS-debug kernels. --=20 wca --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTXxP8ACgkQF47idPgWcsU9/gCeP/BXPHDS3WbLjSexSOw7Xi2r JXsAoJbQXOVdAQQvKgVkLcrMDPNhNFVA =OPgo -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7-- From owner-freebsd-fs@FreeBSD.ORG Sun Feb 8 21:00:26 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 286AD994 for ; Sun, 8 Feb 2015 21:00:26 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F1D97A3A for ; Sun, 8 Feb 2015 21:00:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t18L0PsB077938 for ; Sun, 8 Feb 2015 21:00:25 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201502082100.t18L0PsB077938@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Date: Sun, 08 Feb 2015 21:00:25 +0000 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2015 21:00:26 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f 3 problems total for which you should take action. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 12:48:38 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E7DDF15 for ; Mon, 9 Feb 2015 12:48:38 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0FBCCA7 for ; Mon, 9 Feb 2015 12:48:37 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id D5EE816A5AA for ; Mon, 9 Feb 2015 13:48:34 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CK_VmEFSwRPL; Mon, 9 Feb 2015 13:48:31 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:4c28:fc85:2bef:6785] (unknown [IPv6:2001:4cb8:3:1:4c28:fc85:2bef:6785]) by smtp.digiware.nl (Postfix) with ESMTP id 796F616A4EE for ; Mon, 9 Feb 2015 12:31:00 +0100 (CET) Message-ID: <54D89A69.1000206@digiware.nl> Date: Mon, 09 Feb 2015 12:30:49 +0100 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Panic during fsck in bhyve VM Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 12:48:38 -0000 Hi, Probably due to too many hard-resets of the VM, but I've got the root fs of one of my VMs in a real bad state..... Even where recovery with fsck does not lead to the wanted result. Recovering might be interesting, but not essential since it is just a testing image. The traceback is below. I've saved the image, en getting it online is real easy. If this helps in getting UFS/fsck bugs fixed, I'll keep it. Otherwise it is going into /dev/null --WjW WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/vtbd0p2 [rw]... WARNING: / was not properly dismounted Enter full pathname of shell or RETURN for /bin/sh: # fsck / ** /dev/vtbd0p2 USE JOURNAL? [yn] y ** SU+J Recovering /dev/vtbd0p2 ** Reading 33554432 byte journal from inode 4. RECOVER? [yn] y ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. ***** FILE SYSTEM MARKED CLEAN ***** # df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/vtbd0p2 30450552 15277136 12737376 55% / devfs 2 2 0 100% /dev # mount -rw / panic: ufs_dirbad: /: bad dir ino 1364363 at offset 512: mangled entry cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe02332b12b0 vpanic() at vpanic+0x189/frame 0xfffffe02332b1330 panic() at panic+0x43/frame 0xfffffe02332b1390 ufs_lookup_ino() at ufs_lookup_ino+0xecd/frame 0xfffffe02332b14b0 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xf1/frame 0xfffffe02332b14e0 vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfffffe02332b1540 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xf1/frame 0xfffffe02332b1570 lookup() at lookup+0x5c5/frame 0xfffffe02332b1600 namei() at namei+0x526/frame 0xfffffe02332b16c0 vn_open_cred() at vn_open_cred+0xd5/frame 0xfffffe02332b1820 kern_openat() at kern_openat+0x257/frame 0xfffffe02332b19a0 amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe02332b1ab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe02332b1ab0 --- syscall (499, FreeBSD ELF64, sys_openat), rip = 0x800b09fba, rsp = 0x7fffffffe868, rbp = 0x7fffffffe940 --- KDB: enter: panic [ thread pid 19 tid 100051 ] Stopped at kdb_enter+0x3e: movq $0,kdb_why From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 13:19:29 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B15A5703; Mon, 9 Feb 2015 13:19:29 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 9A9ADFA1; Mon, 9 Feb 2015 13:19:29 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NJI00B9ZAKGAS00@hades.sorbs.net>; Mon, 09 Feb 2015 05:24:18 -0800 (PST) Message-id: <54D8B3D8.6000804@sorbs.net> Date: Mon, 09 Feb 2015 14:19:20 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Stefan Esser , "freebsd-fs@freebsd.org" Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> In-reply-to: <54D4BB5A.30409@freebsd.org> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 13:19:29 -0000 Stefan Esser wrote: > > The point were zdb seg faults hints at the data structure that is > corrupt. You may get some output before the seg fault, if you add > a number of -v options (they add up to higher verbosity). > > Else, you may be able to look at the core and identify the function > that fails. You'll most probably need zdb and libzfs compiled with > "-g" to get any useful information from the core, though. > > For my failed pool, I noticed that internal assumptions were > violated, due to some free space occuring in more than one entry. > I had to special case the test in some function to ignore this > situation (I knew that I'd only ever wanted to mount that pool > R/O to rescue my data). But skipping the test did not suffice, > since another assert triggered (after skipping the NULL dereference, > the calculated sum of free space did not match the recorded sum, I > had to disable that assert, too). With these two patches I was able > to recover the pool starting at a TXG less than 100 transactions back, > which was sufficient for my purpose ... > Question is will zdb 'fix' things or is it just a debug utility (for displaying)? If it is just a debug and won't fix anything, I'm quite happy to roll back transactions, question is how (presumably after one finds the corrupt point - I'm quite happy to just do it by hand until I get success - it will save 2+months of work - I did get an output with a date/time that indicates where the rollback would go to...) In the mean time this appears to be working without crashing - it's been running days now... PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 4332 root 209 22 0 23770M 23277M uwait 1 549:07 11.04% zdb -AAA -L -uhdi -FX -e storage Michelle -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 15:14:38 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 962C6EA2; Mon, 9 Feb 2015 15:14:38 +0000 (UTC) Received: from mailout10.t-online.de (mailout10.t-online.de [194.25.134.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 42170EB7; Mon, 9 Feb 2015 15:14:38 +0000 (UTC) Received: from fwd07.aul.t-online.de (fwd07.aul.t-online.de [172.20.27.150]) by mailout10.t-online.de (Postfix) with SMTP id 2F191264C82; Mon, 9 Feb 2015 16:14:29 +0100 (CET) Received: from [192.168.119.11] (TznW-2ZF8h3y1c7+GZuaA0V6Qk09SglEvswuXE9ZI-yjlAd79ICc0UI-ZPS+8XUQDO@[84.154.99.55]) by fwd07.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1YKq2c-2IJ5F20; Mon, 9 Feb 2015 16:14:26 +0100 Message-ID: <54D8CECE.60909@freebsd.org> Date: Mon, 09 Feb 2015 16:14:22 +0100 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Michelle Sullivan , "freebsd-fs@freebsd.org" Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> In-Reply-To: <54D8B3D8.6000804@sorbs.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-ID: TznW-2ZF8h3y1c7+GZuaA0V6Qk09SglEvswuXE9ZI-yjlAd79ICc0UI-ZPS+8XUQDO X-TOI-MSGID: 51a66239-16c2-40fa-894c-37b37e2cc896 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:14:38 -0000 Am 09.02.2015 um 14:19 schrieb Michelle Sullivan: > Stefan Esser wrote: >> >> The point were zdb seg faults hints at the data structure that is >> corrupt. You may get some output before the seg fault, if you add >> a number of -v options (they add up to higher verbosity). >> >> Else, you may be able to look at the core and identify the function >> that fails. You'll most probably need zdb and libzfs compiled with >> "-g" to get any useful information from the core, though. >> >> For my failed pool, I noticed that internal assumptions were >> violated, due to some free space occuring in more than one entry. >> I had to special case the test in some function to ignore this >> situation (I knew that I'd only ever wanted to mount that pool >> R/O to rescue my data). But skipping the test did not suffice, >> since another assert triggered (after skipping the NULL dereference, >> the calculated sum of free space did not match the recorded sum, I >> had to disable that assert, too). With these two patches I was able >> to recover the pool starting at a TXG less than 100 transactions back, >> which was sufficient for my purpose ... >> > > Question is will zdb 'fix' things or is it just a debug utility (for > displaying)? The purpose of zdf is to access the pool without the need to import it (which tends to crash the kernel) and to possibly identify a safe TXG to go back to. Once you have found that zdb survives accesses to critical data structures of your pool, you can then try to import the pool to rescue your data. > If it is just a debug and won't fix anything, I'm quite happy to roll > back transactions, question is how (presumably after one finds the > corrupt point - I'm quite happy to just do it by hand until I get > success - it will save 2+months of work - I did get an output with a > date/time that indicates where the rollback would go to...) > > In the mean time this appears to be working without crashing - it's been > running days now... > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > COMMAND > 4332 root 209 22 0 23770M 23277M uwait 1 549:07 11.04% > zdb -AAA -L -uhdi -FX -e storage Options -u and -h do not take much time, -i depends on how much was in the intent log (and recovery should be possible without, if your kernel is not too old with regard to supported ZFS features). zdb -d takes a long time, and if it succeeds, you should be able to recover your data. But zdb -m should also run to completion (and ISTR, in my case that was where my kernel blew up trying to import the pool). Using the debugger to analyze the failed instruction let me work around the inconsistency with two small patches (one skipped a consistency check, the second fixed up the sum of free space which was miscalculated due to the free block that lead to the panic being omitted). After I had these patches tested with zdb, I was able to import the pool into a kernel that included these exact patches. You obviously do not want to perform any other activities with the patched kernel, since it lacks some internal checks - it is purely required for the one time backup operation of the failed pool. So, zdb and even the patches that make zdb dump your pool's internal state will not directly lead to access to your data. But if you manage to print all state with "zdb -dm", chances are very good, that you'll be able to import the pool - possibly with temporary hacks to libzfs that skip corrupt data elements (if not strictly required for read accesses to your data). After that succeeded, you have a good chance to copy off your data using a kernel that has the exact same patches in the ZFS driver ... (if any are required, as in my case). Regards, STefan From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 15:14:48 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34199F0C for ; Mon, 9 Feb 2015 15:14:48 +0000 (UTC) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B331EEBA for ; Mon, 9 Feb 2015 15:14:47 +0000 (UTC) X-AuditID: 1209190f-f793f6d000006ae0-c7-54d8cdb1aa94 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 82.98.27360.1BDC8D45; Mon, 9 Feb 2015 10:09:37 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id t19F9bgE011810; Mon, 9 Feb 2015 10:09:37 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t19F9Y41025417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 9 Feb 2015 10:09:36 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t19F9YHk022147; Mon, 9 Feb 2015 10:09:34 -0500 (EST) Date: Mon, 9 Feb 2015 10:09:33 -0500 (EST) From: Benjamin Kaduk To: Willem Jan Withagen Subject: Re: Panic during fsck in bhyve VM In-Reply-To: <54D89A69.1000206@digiware.nl> Message-ID: References: <54D89A69.1000206@digiware.nl> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOIsWRmVeSWpSXmKPExsUixG6norvx7I0Qg0VLbCyOPf7JZvF06jxm ByaPd2dvMnnM+DSfJYApissmJTUnsyy1SN8ugSvj8TTrgkViFRN21DYwtgh1MXJwSAiYSCy5 Y9nFyAlkiklcuLeerYuRi0NIYDGTxItLm5lAEkICGxglbtxjhLAPMkn8fcMFYddLXJy9GCzO IqAlseXOAmYQm01ARWLmm41sILaIgKbEht6bzCC7mAWkJO6srQAJCwOVr+t8zwJicwpoS5z9 uQpsFa+Ag8SUhzOh1mpJ/Hr4AswWFdCRWL1/CgtEjaDEyZlPwGxmoJrl07exTGAUnIUkNQtJ agEj0ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdE73czBK91JTSTYyg8OSU5N/B+O2g0iFGAQ5G JR7eC5+vhwixJpYVV+YeYpTkYFIS5Y04fSNEiC8pP6UyI7E4I76oNCe1+BCjBAezkgiv6VKg HG9KYmVValE+TEqag0VJnHfTD74QIYH0xJLU7NTUgtQimKwMB4eSBG/FGaBGwaLU9NSKtMyc EoQ0EwcnyHAeoOENIDW8xQWJucWZ6RD5U4yKUuK8CSAJAZBERmkeXC8sfbxiFAd6RZj3EUgV DzD1wHW/AhrMBDS4oABscEkiQkqqgXFORvUsSdFyl2+FuRt2Gx0QeDklaaX35d3vVu2pvvPU +9Bu/Tu1Yh/vds5YzW+yrEPOnj9XouKNfk96vYpIzQS92S75LE0P2fgCW+bVWl/603pa1a1/ mt4jf5NFM08dFpf5edZIdNmRVsaO/d+V2yuSvFYw/j9hvueLC4Otf/axwm+Pd6rsC1NiKc5I NNRiLipOBAC8RUov+gIAAA== Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:14:48 -0000 On Mon, 9 Feb 2015, Willem Jan Withagen wrote: > Hi, > > Probably due to too many hard-resets of the VM, but I've got the root fs of > one of my VMs in a real bad state..... > Even where recovery with fsck does not lead to the wanted result. > > Recovering might be interesting, but not essential since it is just a testing > image. > > The traceback is below. I've saved the image, en getting it online is real > easy. > > If this helps in getting UFS/fsck bugs fixed, I'll keep it. > Otherwise it is going into /dev/null > > --WjW > > > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from ufs:/dev/vtbd0p2 [rw]... > WARNING: / was not properly dismounted > Enter full pathname of shell or RETURN for /bin/sh: > # fsck / > ** /dev/vtbd0p2 > > USE JOURNAL? [yn] y > > ** SU+J Recovering /dev/vtbd0p2 > ** Reading 33554432 byte journal from inode 4. > > RECOVER? [yn] y > > ** Building recovery table. > ** Resolving unreferenced inode list. > ** Processing journal entries. > > ***** FILE SYSTEM MARKED CLEAN ***** > # df > Filesystem 512-blocks Used Avail Capacity Mounted on > /dev/vtbd0p2 30450552 15277136 12737376 55% / > devfs 2 2 0 100% /dev > # mount -rw / > panic: ufs_dirbad: /: bad dir ino 1364363 at offset 512: mangled entry This does not seem consistent with the subject line of the email. The first thing to try is to run fsck without using the journal. -Ben Kaduk > cpuid = 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe02332b12b0 > vpanic() at vpanic+0x189/frame 0xfffffe02332b1330 > panic() at panic+0x43/frame 0xfffffe02332b1390 > ufs_lookup_ino() at ufs_lookup_ino+0xecd/frame 0xfffffe02332b14b0 > VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xf1/frame 0xfffffe02332b14e0 > vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfffffe02332b1540 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xf1/frame 0xfffffe02332b1570 > lookup() at lookup+0x5c5/frame 0xfffffe02332b1600 > namei() at namei+0x526/frame 0xfffffe02332b16c0 > vn_open_cred() at vn_open_cred+0xd5/frame 0xfffffe02332b1820 > kern_openat() at kern_openat+0x257/frame 0xfffffe02332b19a0 > amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe02332b1ab0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe02332b1ab0 > --- syscall (499, FreeBSD ELF64, sys_openat), rip = 0x800b09fba, rsp = > 0x7fffffffe868, rbp = 0x7fffffffe940 --- > KDB: enter: panic > [ thread pid 19 tid 100051 ] > Stopped at kdb_enter+0x3e: movq $0,kdb_why > _______________________________________________ > 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 Mon Feb 9 15:39:16 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EF56050E; Mon, 9 Feb 2015 15:39:16 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id D8B0716A; Mon, 9 Feb 2015 15:39:16 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NJI00BBEH1LAS00@hades.sorbs.net>; Mon, 09 Feb 2015 07:44:10 -0800 (PST) Message-id: <54D8D4A1.9090106@sorbs.net> Date: Mon, 09 Feb 2015 16:39:13 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Stefan Esser Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> In-reply-to: <54D8CECE.60909@freebsd.org> Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:39:17 -0000 Stefan Esser wrote: > Am 09.02.2015 um 14:19 schrieb Michelle Sullivan: > >> Stefan Esser wrote: >> >>> The point were zdb seg faults hints at the data structure that is >>> corrupt. You may get some output before the seg fault, if you add >>> a number of -v options (they add up to higher verbosity). >>> >>> Else, you may be able to look at the core and identify the function >>> that fails. You'll most probably need zdb and libzfs compiled with >>> "-g" to get any useful information from the core, though. >>> >>> For my failed pool, I noticed that internal assumptions were >>> violated, due to some free space occuring in more than one entry. >>> I had to special case the test in some function to ignore this >>> situation (I knew that I'd only ever wanted to mount that pool >>> R/O to rescue my data). But skipping the test did not suffice, >>> since another assert triggered (after skipping the NULL dereference, >>> the calculated sum of free space did not match the recorded sum, I >>> had to disable that assert, too). With these two patches I was able >>> to recover the pool starting at a TXG less than 100 transactions back, >>> which was sufficient for my purpose ... >>> >>> >> Question is will zdb 'fix' things or is it just a debug utility (for >> displaying)? >> > > The purpose of zdf is to access the pool without the need to import > it (which tends to crash the kernel) and to possibly identify a safe > TXG to go back to. Once you have found that zdb survives accesses to > critical data structures of your pool, you can then try to import the > pool to rescue your data. > > >> If it is just a debug and won't fix anything, I'm quite happy to roll >> back transactions, question is how (presumably after one finds the >> corrupt point - I'm quite happy to just do it by hand until I get >> success - it will save 2+months of work - I did get an output with a >> date/time that indicates where the rollback would go to...) >> >> In the mean time this appears to be working without crashing - it's been >> running days now... >> >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU >> COMMAND >> 4332 root 209 22 0 23770M 23277M uwait 1 549:07 11.04% >> zdb -AAA -L -uhdi -FX -e storage >> > > Options -u and -h do not take much time, -i depends on how much was > in the intent log (and recovery should be possible without, if your > kernel is not too old with regard to supported ZFS features). > > zdb -d takes a long time, and if it succeeds, you should be able to > recover your data. But zdb -m should also run to completion (and ISTR, > in my case that was where my kernel blew up trying to import the pool). > > Using the debugger to analyze the failed instruction let me work around > the inconsistency with two small patches (one skipped a consistency > check, the second fixed up the sum of free space which was miscalculated > due to the free block that lead to the panic being omitted). > > After I had these patches tested with zdb, I was able to import the pool > into a kernel that included these exact patches. You obviously do not > want to perform any other activities with the patched kernel, since it > lacks some internal checks - it is purely required for the one time > backup operation of the failed pool. > > > So, zdb and even the patches that make zdb dump your pool's internal > state will not directly lead to access to your data. But if you manage > to print all state with "zdb -dm", chances are very good, that you'll > be able to import the pool - possibly with temporary hacks to libzfs > that skip corrupt data elements (if not strictly required for read > accesses to your data). > > After that succeeded, you have a good chance to copy off your data > using a kernel that has the exact same patches in the ZFS driver ... > (if any are required, as in my case). > > Yeah -m crashes. The kernel will not crash it just refuses to import. zdb crashes with some options (or without others) ... question is how to get the import to succeed with a rollback of transactions to clean up the transaction DB - realistically there should be a maximum of 10 transactions that caused the issue as that's the length of the queue (kernel param) and data was lost up to that 10.... What I need to do is get it to recover to how it was before the metadb was corrupted - and if I am right it will be an incomplete write to the metadb that is blocking it (so the last transaction - or maybe last upto 10) are corrupted... Is it possible to discard 10 transactions and import - if so how? Is it possible to rebuild the metadb? The only accesses at the time to the array/fs was a network mount (NFS) where the connected client was torrenting (with less than 10k/s as I think there was only one active torrent at the time)... so if the torrented file is corrupt I can just discard it and start again, and if it's copy-on-write (as I thought zfs was) resetting it to the 'before write' version will just discard a piece of the file which will be replaced/re-downloaded as soon as it is restarted... I have not yet tried a 10.1 kernel - wrote the disk but it seems I can't use an apple superdrive as a boot rom on a PC... Michelle -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 15:40:50 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 301EE585 for ; Mon, 9 Feb 2015 15:40:50 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CD532207 for ; Mon, 9 Feb 2015 15:40:49 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id E713216A403; Mon, 9 Feb 2015 16:40:40 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0980e4UXcvC; Mon, 9 Feb 2015 16:40:39 +0100 (CET) Received: from [192.168.101.102] (unknown [192.168.101.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 9198316A401; Mon, 9 Feb 2015 16:40:39 +0100 (CET) Message-ID: <54D8D4F9.9070901@digiware.nl> Date: Mon, 09 Feb 2015 16:40:41 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Benjamin Kaduk Subject: Re: Panic during fsck in bhyve VM References: <54D89A69.1000206@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:40:50 -0000 On 9-2-2015 16:09, Benjamin Kaduk wrote: > On Mon, 9 Feb 2015, Willem Jan Withagen wrote: > >> Hi, >> >> Probably due to too many hard-resets of the VM, but I've got the root fs of >> one of my VMs in a real bad state..... >> Even where recovery with fsck does not lead to the wanted result. >> >> Recovering might be interesting, but not essential since it is just a testing >> image. >> >> The traceback is below. I've saved the image, en getting it online is real >> easy. >> >> If this helps in getting UFS/fsck bugs fixed, I'll keep it. >> Otherwise it is going into /dev/null >> >> --WjW >> >> >> WARNING: WITNESS option enabled, expect reduced performance. >> Trying to mount root from ufs:/dev/vtbd0p2 [rw]... >> WARNING: / was not properly dismounted >> Enter full pathname of shell or RETURN for /bin/sh: >> # fsck / >> ** /dev/vtbd0p2 >> >> USE JOURNAL? [yn] y >> >> ** SU+J Recovering /dev/vtbd0p2 >> ** Reading 33554432 byte journal from inode 4. >> >> RECOVER? [yn] y >> >> ** Building recovery table. >> ** Resolving unreferenced inode list. >> ** Processing journal entries. >> >> ***** FILE SYSTEM MARKED CLEAN ***** >> # df >> Filesystem 512-blocks Used Avail Capacity Mounted on >> /dev/vtbd0p2 30450552 15277136 12737376 55% / >> devfs 2 2 0 100% /dev >> # mount -rw / >> panic: ufs_dirbad: /: bad dir ino 1364363 at offset 512: mangled entry > > This does not seem consistent with the subject line of the email. > > The first thing to try is to run fsck without using the journal. Oke, You are correct that I worded the title badly. The system actually crashes right away after fsck and going to R/W for the disc. I appreciate the input to running without journal. But there is very little I can find in the manualpages about that? fsck or fsck_ufs. But I would expect fsck "to do the smart thing", and report errors during fixing. And otherwise return a correct FS. --WjW > -Ben Kaduk > >> cpuid = 1 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe02332b12b0 >> vpanic() at vpanic+0x189/frame 0xfffffe02332b1330 >> panic() at panic+0x43/frame 0xfffffe02332b1390 >> ufs_lookup_ino() at ufs_lookup_ino+0xecd/frame 0xfffffe02332b14b0 >> VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xf1/frame 0xfffffe02332b14e0 >> vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfffffe02332b1540 >> VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xf1/frame 0xfffffe02332b1570 >> lookup() at lookup+0x5c5/frame 0xfffffe02332b1600 >> namei() at namei+0x526/frame 0xfffffe02332b16c0 >> vn_open_cred() at vn_open_cred+0xd5/frame 0xfffffe02332b1820 >> kern_openat() at kern_openat+0x257/frame 0xfffffe02332b19a0 >> amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe02332b1ab0 >> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe02332b1ab0 >> --- syscall (499, FreeBSD ELF64, sys_openat), rip = 0x800b09fba, rsp = >> 0x7fffffffe868, rbp = 0x7fffffffe940 --- >> KDB: enter: panic >> [ thread pid 19 tid 100051 ] >> Stopped at kdb_enter+0x3e: movq $0,kdb_why >> _______________________________________________ >> 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 Mon Feb 9 15:44:51 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE512635 for ; Mon, 9 Feb 2015 15:44:51 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7456D23D for ; Mon, 9 Feb 2015 15:44:51 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.9/8.14.9) with ESMTP id t19FinOK030675; Mon, 9 Feb 2015 10:44:49 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <54D8D5DE.4040906@sentex.net> Date: Mon, 09 Feb 2015 10:44:30 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Michelle Sullivan Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> In-Reply-To: <54D8D4A1.9090106@sorbs.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.75 Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:44:51 -0000 On 2/9/2015 10:39 AM, Michelle Sullivan wrote: > > I have not yet tried a 10.1 kernel - wrote the disk but it seems I can't > use an apple superdrive as a boot rom on a PC... USB stick ? I find it a lot easier that CDs/DVDs ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 15:58:39 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE6ABB19 for ; Mon, 9 Feb 2015 15:58:39 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 9288D3B5 for ; Mon, 9 Feb 2015 15:58:39 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NJI00BBOHXWAS00@hades.sorbs.net> for freebsd-fs@freebsd.org; Mon, 09 Feb 2015 08:03:33 -0800 (PST) Message-id: <54D8D92C.6030705@sorbs.net> Date: Mon, 09 Feb 2015 16:58:36 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Mike Tancsa Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> In-reply-to: <54D8D5DE.4040906@sentex.net> Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:58:39 -0000 Mike Tancsa wrote: > On 2/9/2015 10:39 AM, Michelle Sullivan wrote: >> >> I have not yet tried a 10.1 kernel - wrote the disk but it seems I can't >> use an apple superdrive as a boot rom on a PC... > > USB stick ? I find it a lot easier that CDs/DVDs > > ---Mike > > Will have to see if I have one large enough... most of mine are 128k ;-) (yes I use them a lot! ;-) ) -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 16:34:21 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB6EDA81; Mon, 9 Feb 2015 16:34:21 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id B3F58A4D; Mon, 9 Feb 2015 16:34:20 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NJI00BC6JLDAS00@hades.sorbs.net>; Mon, 09 Feb 2015 08:39:15 -0800 (PST) Message-id: <54D8E189.40201@sorbs.net> Date: Mon, 09 Feb 2015 17:34:17 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Mike Tancsa Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> In-reply-to: <54D8D92C.6030705@sorbs.net> Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 16:34:21 -0000 Michelle Sullivan wrote: > Mike Tancsa wrote: > >> On 2/9/2015 10:39 AM, Michelle Sullivan wrote: >> >>> I have not yet tried a 10.1 kernel - wrote the disk but it seems I can't >>> use an apple superdrive as a boot rom on a PC... >>> >> USB stick ? I find it a lot easier that CDs/DVDs >> >> ---Mike >> >> >> > Will have to see if I have one large enough... most of mine are 128k ;-) > > (yes I use them a lot! ;-) ) > > > Oh I forgot to mention when I use zfs import -fFX the crashes of the kernel as the same everytime - out of memory (ie panics in an alloc/trying ot alloc) 32G of RAM on the box. Found up a 32G stick, downloading the latest 11.0 snapshot currently... (12/2014 - on *.de servers) Michelle -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 18:17:51 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F2171923 for ; Mon, 9 Feb 2015 18:17:50 +0000 (UTC) Received: from smarthost.TechFak.NET (smarthost.TechFak.NET [IPv6:2001:638:504:2014:ffff::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smarthost.techfak.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8376590E for ; Mon, 9 Feb 2015 18:17:50 +0000 (UTC) Received: from peterfile.RBG.TechFak.NET (peterfile.RBG.TechFak.NET [IPv6:2001:638:504:20f0::60]) by smarthost.TechFak.NET (8.14.4/8.14.4) with ESMTP id t19IHmO1028135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 9 Feb 2015 19:17:48 +0100 Received: from CIT-EC.NET (localhost [127.0.0.1]) by peterfile.RBG.TechFak.NET (8.14.4/8.14.4/Debian-4) with ESMTP id t19IHmXL018376 for ; Mon, 9 Feb 2015 19:17:48 +0100 Received: (from sfrey@localhost) by CIT-EC.NET (8.14.4/8.14.4/Submit) id t19IHlGX018375 for freebsd-fs@freebsd.org; Mon, 9 Feb 2015 19:17:47 +0100 Date: Mon, 9 Feb 2015 19:17:47 +0100 From: Sascha Frey To: freebsd-fs@freebsd.org Subject: Unable to mount kerberized NFS share on Linux from FreeBSD 10.1 box Message-ID: <20150209181747.GB9520@TechFak.Uni-Bielefeld.DE> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 18:17:51 -0000 Hi list, I'm trying to set up a NFS file server for our Linux clients using FreeBSD 10.1. Mounting the NFS filesystem exported from the FreeBSD box works well if using sec=sys, but doesn't work with sec=krb5. I get 'access denied' on the Linux client (tried both Debian Jessie and Ubuntu 14.04): root@penny:~# mount -t nfs -o vers=4,sec=krb5 leonard.fs.cit-ec.net:/export/homes/sfrey /mnt mount.nfs: access denied by server while mounting leonard.fs.cit-ec.net:/export/homes/sfrey root@penny:~# mount -t nfs -o vers=3,sec=krb5 leonard.fs.cit-ec.net:/export/homes/sfrey /mnt mount.nfs: access denied by server while mounting leonard.fs.cit-ec.net:/export/homes/sfrey Mounting kerberized NFS mounts from our other (Linux based) file servers is possible without having any problems. Connectivity to the KDC seems to be OK: [root@leonard ~]# kinit -k nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE [root@leonard ~]# klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE Issued Expires Principal Feb 9 17:51:58 2015 Feb 10 03:51:59 2015 krbtgt/TECHFAK.UNI-BIELEFELD.DE@TECHFAK.UNI-BIELEFELD.DE I found only one error message in /var/log/messages: nfsd: can't register svc name Any idea what may be wrong? Cheers, Sascha The configuration files on the server: /etc/exports: V4: / -sec=sys:krb5:krb5i:krb5p /export/homes/sfrey -sec=sys:krb5 penny.fs.cit-ec.net /etc/rc.conf: nfs_server_enable="YES" nfsv4_server_enable="YES" nfs_server_flags="-u -t -n 6" nfsuserd_enable="YES" nfsuserd_flags="-domain TechFak.Uni-Bielefeld.DE" mountd_enable="YES" mountd_flags="-r" gssd_enable="YES" gssd_flags="-v" /etc/krb5.conf: [libdefaults] default_keytab_name = /etc/krb5.keytab default_realm = TECHFAK.UNI-BIELEFELD.DE allow_weak_crypto = true [realms] TECHFAK.UNI-BIELEFELD.DE = { default_domain = techfak.uni-bielefeld.de } [domain_realm] .techfak.uni-bielefeld.de = TECHFAK.UNI-BIELEFELD.DE techfak.uni-bielefeld.de = TECHFAK.UNI-BIELEFELD.D /etc/krb5.keytab: [root@leonard ~]# ktutil list /etc/krb5.keytab: Vno Type Principal Aliases 2 des-cbc-crc nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE 2 des3-cbc-sha1 nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE 2 des-cbc-crc host/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE 2 des3-cbc-sha1 host/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE 2 des-cbc-crc root/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE 2 des3-cbc-sha1 root/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 19:58:47 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E637CC7 for ; Mon, 9 Feb 2015 19:58:47 +0000 (UTC) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD3AB6B6 for ; Mon, 9 Feb 2015 19:58:46 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id dc16so22887601qab.1 for ; Mon, 09 Feb 2015 11:58:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=1G1NRLa49dFBBMyqn0Wt9lQ2cDi3FFa1HOedlNQ0NnE=; b=i4cIMQ7RQFTCXngD33ytGqHseEizDGkWP85E8iXaYODZSVFeTf0wXwHhJg5x+eL902 lylzgceeprNIERi70Oritz4IouHONBVGilaarodup49AWJ7gJ6TzdTcw458PRMBvpVbm 0/A/pxCS/Y/1Lmaf8HZ/lO7hZLmg8aZZ9SI+7focPiec8ULFD4hUKwRbJ+gBIVUF6oX6 Ez3C50rWDbXFabCZjWbjeZDpMdtZRWedZ3Y3GcXVAkRYSrQ+nPii8UK9H3jl1ZbZn2GL UEyiH3T3NFRdGXkHpl94OGPd7ADLUIknXoACcM73ehmbhDN+NyFXDaLCGEnNURt+sL0G iDyw== X-Received: by 10.229.19.68 with SMTP id z4mr30701045qca.14.1423511918208; Mon, 09 Feb 2015 11:58:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.170.18 with HTTP; Mon, 9 Feb 2015 11:57:58 -0800 (PST) From: Bogdan SOLGA Date: Mon, 9 Feb 2015 21:57:58 +0200 Message-ID: Subject: A few questions about the FreeBSD GlusterFS port and build To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 19:58:47 -0000 Hello, everyone! I have found this thread from June 2014 and tried to build GlusterFS on a local VM, but the build fails with the following error: ./configure: 13107: Syntax error: word unexpected (expecting ")") I have tried to use the latest 'experimental' build from the GlusterFS repo , dated August 11th 2014. I haven't seen any patches for it, I might have missed the page which lists them. Does anyone have any updates on the GlusterFS port on FreeBSD? According to this Twitter post, it seems to work (at least for some platforms and people). Thank you! Regards, Bogdan From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 20:52:48 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78477194 for ; Mon, 9 Feb 2015 20:52:48 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.redhat.com", Issuer "DigiCert SHA2 Extended Validation Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36D94D57 for ; Mon, 9 Feb 2015 20:52:48 +0000 (UTC) Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t19Kqdvg025521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 9 Feb 2015 15:52:40 -0500 Received: from [10.36.5.102] (vpn1-5-102.ams2.redhat.com [10.36.5.102]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t19Kqafj018684 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 9 Feb 2015 15:52:37 -0500 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: A few questions about the FreeBSD GlusterFS port and build From: Justin Clift In-Reply-To: Date: Mon, 9 Feb 2015 20:52:36 +0000 Content-Transfer-Encoding: 7bit Message-Id: References: To: Bogdan SOLGA X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 Cc: freebsd-fs@freebsd.org, craig001@lerwick.hopto.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 20:52:48 -0000 On 9 Feb 2015, at 19:57, Bogdan SOLGA wrote: > Hello, everyone! > > I have found this > > thread from June 2014 and tried to build GlusterFS on a local VM, but the > build fails with the following error: > > ./configure: 13107: Syntax error: word unexpected (expecting ")") > > I have tried to use the latest 'experimental' build from the GlusterFS repo > , dated August 11th > 2014. I haven't seen any patches for it, I might have missed the page which > lists them. > > Does anyone have any updates on the GlusterFS port on FreeBSD? According to > this Twitter post, > it seems to work (at least for some platforms and people). In theory :D, the patches for getting it working were merged a while back, so the "normal" everyday tarball is supposed to compile fine. There is a port for it around somewhere, too though I've been on leave until recently and not caught up with where that's at. Craig Butler (CC'd) is the guy in the know about that. :) We also submitted a patch for FreeBSD's fuse module a few months ago, but it doesn't seem to have been looked over yet. :( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192701 Does that help? :) Regards and best wishes, Justin Clift > Thank you! > > Regards, > Bogdan > _______________________________________________ > 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" -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 20:54:30 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 49CAE20A for ; Mon, 9 Feb 2015 20:54:30 +0000 (UTC) Received: from gw.catspoiler.org (cl-1657.chi-02.us.sixxs.net [IPv6:2001:4978:f:678::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB1DFD69 for ; Mon, 9 Feb 2015 20:54:29 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id t19KsDHR014351; Mon, 9 Feb 2015 12:54:17 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201502092054.t19KsDHR014351@gw.catspoiler.org> Date: Mon, 9 Feb 2015 12:54:13 -0800 (PST) From: Don Lewis Subject: Re: Panic during fsck in bhyve VM To: wjw@digiware.nl In-Reply-To: <54D8D4F9.9070901@digiware.nl> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 20:54:30 -0000 On 9 Feb, Willem Jan Withagen wrote: > On 9-2-2015 16:09, Benjamin Kaduk wrote: >> On Mon, 9 Feb 2015, Willem Jan Withagen wrote: >> >>> Hi, >>> >>> Probably due to too many hard-resets of the VM, but I've got the >>> root fs of one of my VMs in a real bad state..... >>> Even where recovery with fsck does not lead to the wanted result. >>> >>> Recovering might be interesting, but not essential since it is just >>> a testing image. >>> >>> The traceback is below. I've saved the image, en getting it online >>> is real easy. >>> >>> If this helps in getting UFS/fsck bugs fixed, I'll keep it. >>> Otherwise it is going into /dev/null >>> >>> --WjW >>> >>> >>> WARNING: WITNESS option enabled, expect reduced performance. >>> Trying to mount root from ufs:/dev/vtbd0p2 [rw]... >>> WARNING: / was not properly dismounted >>> Enter full pathname of shell or RETURN for /bin/sh: >>> # fsck / >>> ** /dev/vtbd0p2 >>> >>> USE JOURNAL? [yn] y >>> >>> ** SU+J Recovering /dev/vtbd0p2 >>> ** Reading 33554432 byte journal from inode 4. >>> >>> RECOVER? [yn] y >>> >>> ** Building recovery table. >>> ** Resolving unreferenced inode list. >>> ** Processing journal entries. >>> >>> ***** FILE SYSTEM MARKED CLEAN ***** >>> # df >>> Filesystem 512-blocks Used Avail Capacity Mounted on >>> /dev/vtbd0p2 30450552 15277136 12737376 55% / >>> devfs 2 2 0 100% /dev >>> # mount -rw / >>> panic: ufs_dirbad: /: bad dir ino 1364363 at offset 512: mangled >>> entry >> >> This does not seem consistent with the subject line of the email. >> >> The first thing to try is to run fsck without using the journal. > > Oke, > > You are correct that I worded the title badly. > The system actually crashes right away after fsck and going to R/W for > the disc. > > I appreciate the input to running without journal. > But there is very little I can find in the manualpages about that? > fsck or fsck_ufs. fsck is fine > But I would expect fsck "to do the smart thing", and report errors > during fixing. And otherwise return a correct FS. If you tell fsck to use the journal, it assumes that the filesystem is basically in good shape and it just needs to take care of the transactions in the journal. That way the the reboot is much quicker because it doesn't have to wait for a full fsck. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 21:21:37 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72E9DDD4 for ; Mon, 9 Feb 2015 21:21:37 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 5AF2CDE for ; Mon, 9 Feb 2015 21:21:36 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NJI00D0VWW5EQ00@hades.sorbs.net> for freebsd-fs@freebsd.org; Mon, 09 Feb 2015 13:26:30 -0800 (PST) Message-id: <54D924DD.4000205@sorbs.net> Date: Mon, 09 Feb 2015 22:21:33 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Mike Tancsa Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> In-reply-to: <54D8E189.40201@sorbs.net> Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 21:21:37 -0000 Michelle Sullivan wrote: > Michelle Sullivan wrote: > >> Mike Tancsa wrote: >> >> >>> On 2/9/2015 10:39 AM, Michelle Sullivan wrote: >>> >>> >>>> I have not yet tried a 10.1 kernel - wrote the disk but it seems I can't >>>> use an apple superdrive as a boot rom on a PC... >>>> >>>> >>> USB stick ? I find it a lot easier that CDs/DVDs >>> >>> ---Mike >>> >>> >>> >>> >> Will have to see if I have one large enough... most of mine are 128k ;-) >> >> (yes I use them a lot! ;-) ) >> >> >> >> > Oh I forgot to mention when I use zfs import -fFX the crashes of the > kernel as the same everytime - out of memory (ie panics in an > alloc/trying ot alloc) 32G of RAM on the box. > > Found up a 32G stick, downloading the latest 11.0 snapshot currently... > (12/2014 - on *.de servers) > > Michelle > > So far (few hours in) zfs import -fFX has not faulted with this image... it's running out of memory currently about 16G of 32G- however 9.2-P15 kernel died within minutes... out of memory (all 32G and swap) so am more optimistic at the moment... Fingers Crossed. Regards, Michelle -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 21:40:19 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A73BB96F for ; Mon, 9 Feb 2015 21:40:19 +0000 (UTC) Received: from mx.bsdtec.net (mx.bsdtec.net [174.34.171.65]) by mx1.freebsd.org (Postfix) with ESMTP id 643412A5 for ; Mon, 9 Feb 2015 21:40:19 +0000 (UTC) Received: from localhost (mx.bsdtec.net [172.16.32.2]) by mx.bsdtec.net (Postfix) with ESMTP id 43664489875; Mon, 9 Feb 2015 21:34:40 +0000 (UTC) Received: from mx.bsdtec.net ([172.16.32.2]) by localhost (mx.bsdtec.net [172.16.32.2]) (amavisd-new, port 10032) with ESMTP id jJYcdtGkusnB; Mon, 9 Feb 2015 21:34:39 +0000 (UTC) Received: from localhost (mx.bsdtec.net [172.16.32.2]) by mx.bsdtec.net (Postfix) with ESMTP id 50210489898; Mon, 9 Feb 2015 21:34:39 +0000 (UTC) X-Virus-Scanned: amavisd-new at bsdtec.net Received: from mx.bsdtec.net ([172.16.32.2]) by localhost (mx.bsdtec.net [172.16.32.2]) (amavisd-new, port 10026) with ESMTP id 92OBT47NWuVq; Mon, 9 Feb 2015 21:34:39 +0000 (UTC) Received: from [192.168.1.111] (bsdtec.plus.com [84.92.41.141]) by mx.bsdtec.net (Postfix) with ESMTPSA id 70468489875; Mon, 9 Feb 2015 21:34:38 +0000 (UTC) Message-ID: <1423517676.3855.6.camel@atlas.lerwick.hopto.org> Subject: Re: A few questions about the FreeBSD GlusterFS port and build From: Craig Butler To: Justin Clift Date: Mon, 09 Feb 2015 21:34:36 +0000 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: Bogdan SOLGA , freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 21:40:19 -0000 On Mon, 2015-02-09 at 20:52 +0000, Justin Clift wrote: > On 9 Feb 2015, at 19:57, Bogdan SOLGA wrote: > > Hello, everyone! > > > > I have found this > > > > thread from June 2014 and tried to build GlusterFS on a local VM, but the > > build fails with the following error: > > > > ./configure: 13107: Syntax error: word unexpected (expecting ")") > > > > I have tried to use the latest 'experimental' build from the GlusterFS repo > > , dated August 11th > > 2014. I haven't seen any patches for it, I might have missed the page which > > lists them. > > > > Does anyone have any updates on the GlusterFS port on FreeBSD? According to > > this Twitter post, > > it seems to work (at least for some platforms and people). > > In theory :D, the patches for getting it working were merged a while back, > so the "normal" everyday tarball is supposed to compile fine. > > There is a port for it around somewhere, too though I've been on leave until > recently and not caught up with where that's at. Craig Butler (CC'd) is the > guy in the know about that. :) > > We also submitted a patch for FreeBSD's fuse module a few months ago, but it > doesn't seem to have been looked over yet. :( > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192701 > > Does that help? :) > > Regards and best wishes, > > Justin Clift > > > > Thank you! > > > > Regards, > > Bogdan > > _______________________________________________ > > 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" > > -- > GlusterFS - http://www.gluster.org > > An open source, distributed file system scaling to several > petabytes, and handling thousands of clients. > > My personal twitter: twitter.com/realjustinclift > Hello Justin et al The commits to bugs.freebsd.org seem to be taking an age to action. I suspect the bug review folks are fairly busy at the moment. We have a port candidate PR in progress; https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194409 Unfortunately only seems to be working on 10.1-RELEASE amd64 at the moment. I will work on it this week and see if I can get it to compile on the other releases and archs. Hopefully if I give hrs@ a nudge we can get something finally committed. Bogdan, please feel free to test the port out and send us your feedback. Kind Regards Craig Butler From owner-freebsd-fs@FreeBSD.ORG Mon Feb 9 23:24:11 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B727CA4 for ; Mon, 9 Feb 2015 23:24:11 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 0ED6074 for ; Mon, 9 Feb 2015 23:24:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BGBQDvQNlU/95baINcg1haBIJ+v3IKhSdKAoFfAQEBAQEBfIQMAQEBAwEBAQEgKyALGw4KAgINGQIpAQkmBggHBAEcBIgECA21fZZPAQEBAQEBAQECAQEBAQEBAQEBARiBIY4GAQEbNAeCaIFCBYoniESDPYNtkSIihAwgMQEGgQQ5fgEBAQ X-IronPort-AV: E=Sophos;i="5.09,546,1418101200"; d="scan'208";a="191641829" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 09 Feb 2015 18:24:03 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id A3A7DB3FE0; Mon, 9 Feb 2015 18:24:03 -0500 (EST) Date: Mon, 9 Feb 2015 18:24:03 -0500 (EST) From: Rick Macklem To: Sascha Frey Message-ID: <2131985962.2999032.1423524243651.JavaMail.root@uoguelph.ca> In-Reply-To: <20150209181747.GB9520@TechFak.Uni-Bielefeld.DE> Subject: Re: Unable to mount kerberized NFS share on Linux from FreeBSD 10.1 box MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 23:24:11 -0000 Sascha Frey wrote: > Hi list, > > I'm trying to set up a NFS file server for our Linux clients using > FreeBSD 10.1. > > Mounting the NFS filesystem exported from the FreeBSD box works well > if using sec=sys, but doesn't work with sec=krb5. > > I get 'access denied' on the Linux client (tried both Debian Jessie > and > Ubuntu 14.04): > > root@penny:~# mount -t nfs -o vers=4,sec=krb5 > leonard.fs.cit-ec.net:/export/homes/sfrey /mnt > mount.nfs: access denied by server while mounting > leonard.fs.cit-ec.net:/export/homes/sfrey > root@penny:~# mount -t nfs -o vers=3,sec=krb5 > leonard.fs.cit-ec.net:/export/homes/sfrey /mnt > mount.nfs: access denied by server while mounting > leonard.fs.cit-ec.net:/export/homes/sfrey > > Mounting kerberized NFS mounts from our other (Linux based) file > servers > is possible without having any problems. > > Connectivity to the KDC seems to be OK: > [root@leonard ~]# kinit -k > nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > [root@leonard ~]# klist > Credentials cache: FILE:/tmp/krb5cc_0 > Principal: nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > > Issued Expires Principal > Feb 9 17:51:58 2015 Feb 10 03:51:59 2015 > krbtgt/TECHFAK.UNI-BIELEFELD.DE@TECHFAK.UNI-BIELEFELD.DE > > I found only one error message in /var/log/messages: > nfsd: can't register svc name > Well, this message indicates it isn't going to work. (This message means the nfsd couldn't register with the gssd daemon, so kerberized NFS won't work.) It is generated when the nfsd is started. The most common cause would be the gssd daemon not running when the nfsd daemon is started. If the gssd was running when the nfsd was started and this message is logged, there is a debug option on gssd that makes it chatty and that might indicate why it is failing. Also, there is this wiki. It is somewhat out of date, but I don't think anything has changed w.r.t. the server side. (I'm not sure what the current status is w.r.t. keytab entries encrypted in newer ways than des-cbc-crc is.) https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup Good luck with it, rick > > Any idea what may be wrong? > > > > > > Cheers, > Sascha > > > > The configuration files on the server: > > /etc/exports: > V4: / -sec=sys:krb5:krb5i:krb5p > /export/homes/sfrey -sec=sys:krb5 penny.fs.cit-ec.net > > /etc/rc.conf: > nfs_server_enable="YES" > nfsv4_server_enable="YES" > nfs_server_flags="-u -t -n 6" > nfsuserd_enable="YES" > nfsuserd_flags="-domain TechFak.Uni-Bielefeld.DE" > mountd_enable="YES" > mountd_flags="-r" > gssd_enable="YES" > gssd_flags="-v" > > /etc/krb5.conf: > [libdefaults] > default_keytab_name = /etc/krb5.keytab > default_realm = TECHFAK.UNI-BIELEFELD.DE > allow_weak_crypto = true > > [realms] > TECHFAK.UNI-BIELEFELD.DE = { > default_domain = techfak.uni-bielefeld.de > } > > [domain_realm] > .techfak.uni-bielefeld.de = TECHFAK.UNI-BIELEFELD.DE > techfak.uni-bielefeld.de = TECHFAK.UNI-BIELEFELD.D > > > /etc/krb5.keytab: > [root@leonard ~]# ktutil list > /etc/krb5.keytab: > > Vno Type Principal > Aliases > 2 des-cbc-crc > nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des3-cbc-sha1 > nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des-cbc-crc > host/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des3-cbc-sha1 > host/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des-cbc-crc > root/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des3-cbc-sha1 > root/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > > _______________________________________________ > 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 Mon Feb 9 23:30:04 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F334AAD for ; Mon, 9 Feb 2015 23:30:04 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id A353ED8 for ; Mon, 9 Feb 2015 23:30:04 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BGBQCmQdlU/95baINcg1haBIJ+v3IKhSdKAoFgAQEBAQEBfIQNAQEEAQEBICsgCxsOCgICDRkCKQEJJgYIBwQBHASIDA21e5ZRAQEBAQEBBAEBAQEBAQEBGoEhjgYBARs0B4JogUIFhVOEVIhEgz2DNzaNZIM+IoQMIDEBBoEEOX4BAQE X-IronPort-AV: E=Sophos;i="5.09,546,1418101200"; d="scan'208";a="189879418" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 09 Feb 2015 18:29:59 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id DB213B3F07; Mon, 9 Feb 2015 18:29:57 -0500 (EST) Date: Mon, 9 Feb 2015 18:29:57 -0500 (EST) From: Rick Macklem To: Sascha Frey Message-ID: <1722953463.3002240.1423524597892.JavaMail.root@uoguelph.ca> In-Reply-To: <20150209181747.GB9520@TechFak.Uni-Bielefeld.DE> Subject: Re: Unable to mount kerberized NFS share on Linux from FreeBSD 10.1 box MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 23:30:05 -0000 Sascha Frey wrote: > Hi list, > > I'm trying to set up a NFS file server for our Linux clients using > FreeBSD 10.1. > > Mounting the NFS filesystem exported from the FreeBSD box works well > if using sec=sys, but doesn't work with sec=krb5. > > I get 'access denied' on the Linux client (tried both Debian Jessie > and > Ubuntu 14.04): > > root@penny:~# mount -t nfs -o vers=4,sec=krb5 > leonard.fs.cit-ec.net:/export/homes/sfrey /mnt > mount.nfs: access denied by server while mounting > leonard.fs.cit-ec.net:/export/homes/sfrey > root@penny:~# mount -t nfs -o vers=3,sec=krb5 > leonard.fs.cit-ec.net:/export/homes/sfrey /mnt > mount.nfs: access denied by server while mounting > leonard.fs.cit-ec.net:/export/homes/sfrey > > Mounting kerberized NFS mounts from our other (Linux based) file > servers > is possible without having any problems. > > Connectivity to the KDC seems to be OK: > [root@leonard ~]# kinit -k > nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > [root@leonard ~]# klist > Credentials cache: FILE:/tmp/krb5cc_0 > Principal: nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > > Issued Expires Principal > Feb 9 17:51:58 2015 Feb 10 03:51:59 2015 > krbtgt/TECHFAK.UNI-BIELEFELD.DE@TECHFAK.UNI-BIELEFELD.DE > > I found only one error message in /var/log/messages: > nfsd: can't register svc name > > > Any idea what may be wrong? > Oh, and a couple more things... FreeBSD only supports RPCSEC_GSS_VERSION1. This should be sufficient, since it is what is required by the NFSv4 RFC. However, I wouldn't be surprised if recent Linux clients decide it isn't good enough for them. (Hopefully if this is the case, there is a way to tell Linux to use version 1.) If none of the suggestions helps, I'd suggest you capture packets via something like: # tcpdump -s 0 -w krbmnt.pcap host running while a mount attempt is done. You can then look at krbmnt.pcap in wireshark to see what is going on the wire. Also, take a look at your KDC logs. That might indicate a problem with encryption type used or similar. It has been tested against Linux and Solaris clients, but not for a couple of years. Again, good luck with it, rick > > > > > Cheers, > Sascha > > > > The configuration files on the server: > > /etc/exports: > V4: / -sec=sys:krb5:krb5i:krb5p > /export/homes/sfrey -sec=sys:krb5 penny.fs.cit-ec.net > > /etc/rc.conf: > nfs_server_enable="YES" > nfsv4_server_enable="YES" > nfs_server_flags="-u -t -n 6" > nfsuserd_enable="YES" > nfsuserd_flags="-domain TechFak.Uni-Bielefeld.DE" > mountd_enable="YES" > mountd_flags="-r" > gssd_enable="YES" > gssd_flags="-v" > > /etc/krb5.conf: > [libdefaults] > default_keytab_name = /etc/krb5.keytab > default_realm = TECHFAK.UNI-BIELEFELD.DE > allow_weak_crypto = true > > [realms] > TECHFAK.UNI-BIELEFELD.DE = { > default_domain = techfak.uni-bielefeld.de > } > > [domain_realm] > .techfak.uni-bielefeld.de = TECHFAK.UNI-BIELEFELD.DE > techfak.uni-bielefeld.de = TECHFAK.UNI-BIELEFELD.D > > > /etc/krb5.keytab: > [root@leonard ~]# ktutil list > /etc/krb5.keytab: > > Vno Type Principal > Aliases > 2 des-cbc-crc > nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des3-cbc-sha1 > nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des-cbc-crc > host/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des3-cbc-sha1 > host/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des-cbc-crc > root/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > 2 des3-cbc-sha1 > root/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > > _______________________________________________ > 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 Tue Feb 10 08:00:59 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6161786D for ; Tue, 10 Feb 2015 08:00:59 +0000 (UTC) Received: from smarthost.TechFak.NET (smarthost.TechFak.NET [IPv6:2001:638:504:2014:ffff::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smarthost.techfak.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E84AE252 for ; Tue, 10 Feb 2015 08:00:58 +0000 (UTC) Received: from peterfile.RBG.TechFak.NET (peterfile.RBG.TechFak.NET [IPv6:2001:638:504:20f0::60]) by smarthost.TechFak.NET (8.14.4/8.14.4) with ESMTP id t1A80sa9001622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 10 Feb 2015 09:00:54 +0100 Received: from CIT-EC.NET (localhost [127.0.0.1]) by peterfile.RBG.TechFak.NET (8.14.4/8.14.4/Debian-4) with ESMTP id t1A80smX009025 for ; Tue, 10 Feb 2015 09:00:54 +0100 Received: (from sfrey@localhost) by CIT-EC.NET (8.14.4/8.14.4/Submit) id t1A80r79009024 for freebsd-fs@freebsd.org; Tue, 10 Feb 2015 09:00:53 +0100 Date: Tue, 10 Feb 2015 09:00:53 +0100 From: Sascha Frey To: freebsd-fs@freebsd.org Subject: Re: Unable to mount kerberized NFS share on Linux from FreeBSD 10.1 box Message-ID: <20150210080053.GA20995@TechFak.Uni-Bielefeld.DE> References: <20150209181747.GB9520@TechFak.Uni-Bielefeld.DE> <2131985962.2999032.1423524243651.JavaMail.root@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2131985962.2999032.1423524243651.JavaMail.root@uoguelph.ca> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 08:00:59 -0000 Rick Macklem wrote: [...] >> I found only one error message in /var/log/messages: >> nfsd: can't register svc name >> >Well, this message indicates it isn't going to work. >(This message means the nfsd couldn't register with the gssd daemon, > so kerberized NFS won't work.) It is generated when the nfsd is >started. > >The most common cause would be the gssd daemon not running when the >nfsd daemon is started. If the gssd was running when the nfsd was started >and this message is logged, there is a debug option on gssd that makes >it chatty and that might indicate why it is failing. gssd was running before nfsd was started. This message does not appear if nfsd starts without gssd running, but it does appear as soon as gssd is started (if nfsd is already running). I started gssd in foreground mode (via gssd -d -v) These messages appear when I start nfsd: gssd_import_name: done major=0x0 minor=0 gssd_acquire_cred: done major=0x70000 minor=0 gssd_release_name: done major=0x0 minor=0 gssd_import_name: done major=0x0 minor=0 gssd_acquire_cred: done major=0x70000 minor=0 gssd_release_name: done major=0x0 minor=0 gssd_import_name: done major=0x0 minor=0 gssd_acquire_cred: done major=0x70000 minor=0 gssd_release_name: done major=0x0 minor=0 No log output when trying to mount NFS share on the Linux machine. I tried to mount it on the server itself. I'm able to mount, but I can't access any files... [root@leonard ~]# mount -o sec=krb5 leonard.fs.cit-ec.net:/export/homes/sfrey /mnt [root@leonard ~]# su - sfrey [sfrey@leonard ~]$ kinit sfrey@TECHFAK.UNI-BIELEFELD.DE's Password: [sfrey@leonard ~]$ ls -lad /mnt ls: /mnt: Permission denied [sfrey@leonard ~]$ klist Credentials cache: FILE:/tmp/krb5cc_21036 Principal: sfrey@TECHFAK.UNI-BIELEFELD.DE Issued Expires Principal Feb 10 08:54:31 2015 Feb 10 18:54:39 2015 krbtgt/TECHFAK.UNI-BIELEFELD.DE@TECHFAK.UNI-BIELEFELD.DE Feb 10 08:54:36 2015 Feb 10 18:54:39 2015 nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > >Also, there is this wiki. It is somewhat out of date, but I don't think >anything has changed w.r.t. the server side. (I'm not sure what the >current status is w.r.t. keytab entries encrypted in newer ways than >des-cbc-crc is.) >https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup I'll take a look into it. Maybe I missed something. Cheers, Sascha From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 10:17:00 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28EFE20E for ; Tue, 10 Feb 2015 10:17:00 +0000 (UTC) Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF06D3DB for ; Tue, 10 Feb 2015 10:16:59 +0000 (UTC) Received: by mail-qg0-f48.google.com with SMTP id a108so25991845qge.7 for ; Tue, 10 Feb 2015 02:16:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2GmWEG795kT7HnrneGiKoeLDvgAuYtTgzW0AZs0Yt6c=; b=ydAzkRakVtCVU6mRnB1yo0D6WnUy2wvnCEIWPgPm68JLynkM3lTHdBVIg00baDAeW6 rcxgojyiXHUytA0pYlI+JlgeAUim1nZ5/18WXl1dGStkEHYVQtQr52H05vOyR+F6KgM5 osiqG+qlyQTluHu2z0xMAiT3Ax3WXboEMb8bwpeffLSOb1LNfhyGGQPsWamDkdp6+zxQ dp5hByo8oxeEzlC9RORKSFQF+JXGUqp9ZXhZHWmd494lA5yIIXqjUgW+yTN1VqUtq8BN mE1PQAj7jaJBrBxLNncPtJMUYb4olWUAL8GmpMkniGYA2c/sAVPSQpplx/QsvwG87tzl Co/g== X-Received: by 10.140.22.234 with SMTP id 97mr48022398qgn.21.1423563418902; Tue, 10 Feb 2015 02:16:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.170.18 with HTTP; Tue, 10 Feb 2015 02:16:18 -0800 (PST) In-Reply-To: <1423517676.3855.6.camel@atlas.lerwick.hopto.org> References: <1423517676.3855.6.camel@atlas.lerwick.hopto.org> From: Bogdan SOLGA Date: Tue, 10 Feb 2015 12:16:18 +0200 Message-ID: Subject: Re: A few questions about the FreeBSD GlusterFS port and build To: Craig Butler Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 10:17:00 -0000 Hello Craig, Justin et all! Thank you for the provided link! I have tried to install it using the provided shar file; the build works, but 'make install fails' with the following error: " On make install: pkg-static: lstat(/tmp/glusterfs/work/stage/usr/local/%%PYTHON_SITELIBDIR%%/gluster/): No such file or directory *** Error code 74 Stop. make: stopped in /tmp/glusterfs " Am I doing something wrong? or have I skipped / missed any steps? Thank you! Kind regards, Bogdan On Mon, Feb 9, 2015 at 11:34 PM, Craig Butler wrote: > On Mon, 2015-02-09 at 20:52 +0000, Justin Clift wrote: > > On 9 Feb 2015, at 19:57, Bogdan SOLGA wrote: > > > Hello, everyone! > > > > > > I have found this > > > > > > thread from June 2014 and tried to build GlusterFS on a local VM, but > the > > > build fails with the following error: > > > > > > ./configure: 13107: Syntax error: word unexpected (expecting ")") > > > > > > I have tried to use the latest 'experimental' build from the GlusterFS > repo > > > , dated August > 11th > > > 2014. I haven't seen any patches for it, I might have missed the page > which > > > lists them. > > > > > > Does anyone have any updates on the GlusterFS port on FreeBSD? > According to > > > this Twitter > post, > > > it seems to work (at least for some platforms and people). > > > > In theory :D, the patches for getting it working were merged a while > back, > > so the "normal" everyday tarball is supposed to compile fine. > > > > There is a port for it around somewhere, too though I've been on leave > until > > recently and not caught up with where that's at. Craig Butler (CC'd) is > the > > guy in the know about that. :) > > > > We also submitted a patch for FreeBSD's fuse module a few months ago, > but it > > doesn't seem to have been looked over yet. :( > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192701 > > > > Does that help? :) > > > > Regards and best wishes, > > > > Justin Clift > > > > > > > Thank you! > > > > > > Regards, > > > Bogdan > > > _______________________________________________ > > > 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" > > > > -- > > GlusterFS - http://www.gluster.org > > > > An open source, distributed file system scaling to several > > petabytes, and handling thousands of clients. > > > > My personal twitter: twitter.com/realjustinclift > > > > Hello Justin et al > > The commits to bugs.freebsd.org seem to be taking an age to action. I > suspect the bug review folks are fairly busy at the moment. > > We have a port candidate PR in progress; > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194409 > > Unfortunately only seems to be working on 10.1-RELEASE amd64 at the > moment. > > I will work on it this week and see if I can get it to compile on the > other releases and archs. Hopefully if I give hrs@ a nudge we can get > something finally committed. > > Bogdan, please feel free to test the port out and send us your feedback. > > Kind Regards > > Craig Butler > > > From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 10:51:34 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F0326C8 for ; Tue, 10 Feb 2015 10:51:34 +0000 (UTC) Received: from mx.bsdtec.net (mx.bsdtec.net [174.34.171.65]) by mx1.freebsd.org (Postfix) with ESMTP id 0BCD09DD for ; Tue, 10 Feb 2015 10:51:34 +0000 (UTC) Received: from localhost (mx.bsdtec.net [172.16.32.2]) by mx.bsdtec.net (Postfix) with ESMTP id 04E4D489898; Tue, 10 Feb 2015 10:51:33 +0000 (UTC) Received: from mx.bsdtec.net ([172.16.32.2]) by localhost (mx.bsdtec.net [172.16.32.2]) (amavisd-new, port 10032) with ESMTP id umpSSfGqwOF7; Tue, 10 Feb 2015 10:51:32 +0000 (UTC) Received: from localhost (mx.bsdtec.net [172.16.32.2]) by mx.bsdtec.net (Postfix) with ESMTP id 158BD4898C0; Tue, 10 Feb 2015 10:51:32 +0000 (UTC) X-Virus-Scanned: amavisd-new at bsdtec.net Received: from mx.bsdtec.net ([172.16.32.2]) by localhost (mx.bsdtec.net [172.16.32.2]) (amavisd-new, port 10026) with ESMTP id Kk7jfXe84tHE; Tue, 10 Feb 2015 10:51:31 +0000 (UTC) Received: from mx.bsdtec.net (mx.bsdtec.net [172.16.32.2]) by mx.bsdtec.net (Postfix) with ESMTP id CB542489898; Tue, 10 Feb 2015 10:51:31 +0000 (UTC) Date: Tue, 10 Feb 2015 10:51:31 +0000 (GMT) From: Craig Butler To: Bogdan SOLGA Message-ID: <15075988.55.1423565761148.JavaMail.craig@w520> In-Reply-To: References: <1423517676.3855.6.camel@atlas.lerwick.hopto.org> Subject: Re: A few questions about the FreeBSD GlusterFS port and build MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.16.32.3] X-Mailer: Zimbra 8.0.4_GA_5718 (Zimbra Desktop/7.2.5_12038_Windows) Thread-Topic: A few questions about the FreeBSD GlusterFS port and build Thread-Index: uwKCEt4n27EnYSUhphUxdvoSJcy0uw== Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 10:51:34 -0000 ----- Original Message ----- > From: "Bogdan SOLGA" > To: "Craig Butler" > Cc: "Justin Clift" , "freebsd-fs" > Sent: Tuesday, 10 February, 2015 10:16:18 AM > Subject: Re: A few questions about the FreeBSD GlusterFS port and build > > > > Hello Craig, Justin et all! > > Thank you for the provided link! I have tried to install it using the > provided shar file; the build works, but 'make install fails' with > the following error: > > > > " > On make install: > > > pkg-static: > lstat(/tmp/glusterfs/work/stage/usr/local/%%PYTHON_SITELIBDIR%%/gluster/): > No such file or directory > *** Error code 74 > > Stop. > make: stopped in /tmp/glusterfs > " > > > Am I doing something wrong? or have I skipped / missed any steps? > > > Thank you! > > > Kind regards, > Bogdan > Hello Bogdan Just to clarify you are using the Commit candidate of GlusterFS port -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149791 and are you just running make install from the glusterfs directory ? The port should pull in Python as a build dependency. Kind Regards Craig Butler From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 12:21:59 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C03231B for ; Tue, 10 Feb 2015 12:21:59 +0000 (UTC) Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DEEE617 for ; Tue, 10 Feb 2015 12:21:59 +0000 (UTC) Received: by mail-qg0-f44.google.com with SMTP id j5so11053688qga.3 for ; Tue, 10 Feb 2015 04:21:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RxkoNCIE5IOPnNffMPOURHtEymBHRhtavJA26Gg5G+8=; b=oH+2uCnaggWdnyFwFr99OxPn9PIMn8zmijzbPFDSkJN0xxkai/DM3v6TLikNROXuwt MwbT0AbWsHdTXMBjwJ+I50o8gdCwluTD2hbyvWrEswAb6Qg0cv276dqw74k/QkkPCC9T t8zTVR9LZtVJY7+ph/JVmgwWb0lJFyHMAyV7s8p1MVb12MsM4NjQVdEyx1zMPTbb+Lvu al1n2t0mWfz8N608AQhXlwzwjoCfNyuCYoVkBZ5aA8oBi6kv5SJ09E+zvzNUTjljcAk9 rCUtUN2JHsi/C3YaeAHDXk/Us1J3tWJYqALI8Q+SjriAjtHXhuDqMCKjtFZW/3yKyIpB jokQ== X-Received: by 10.224.46.132 with SMTP id j4mr37553520qaf.16.1423570918200; Tue, 10 Feb 2015 04:21:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.170.18 with HTTP; Tue, 10 Feb 2015 04:21:18 -0800 (PST) In-Reply-To: <15075988.55.1423565761148.JavaMail.craig@w520> References: <1423517676.3855.6.camel@atlas.lerwick.hopto.org> <15075988.55.1423565761148.JavaMail.craig@w520> From: Bogdan SOLGA Date: Tue, 10 Feb 2015 14:21:18 +0200 Message-ID: Subject: Re: A few questions about the FreeBSD GlusterFS port and build To: Craig Butler Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 12:21:59 -0000 Hello, Craig! I have tried to use the (files from the) commit candidate, as well. With those files, 'make' was not even completed; I don't have the error, as I have tried it on another VM, which is not available for the moment. After seeing that the commit candidate wasn't building, I have tried these 'build' instructions. For these... 'make' works, but 'make install' fails, with the ' > No such file or directory' error (although Python is installed, by the build process). I have tried to reproduce the second issue on a newly created VM, but on this VM the 'portsnap fetch extract' fails with the following error: Extracting snapshot... snap/8bd2f2d1e85bb98a760022703eac8ff47d51700559cfedcb0b158e4eca2fc992.gz: truncated gzip input tar: Error exit delayed from previous errors. ... and I have yet to find a solution for it. Any hints and / or help is appreciated. Regards, Bogdan On Tue, Feb 10, 2015 at 12:51 PM, Craig Butler wrote: > > > ----- Original Message ----- > > From: "Bogdan SOLGA" > > To: "Craig Butler" > > Cc: "Justin Clift" , "freebsd-fs" < > freebsd-fs@freebsd.org> > > Sent: Tuesday, 10 February, 2015 10:16:18 AM > > Subject: Re: A few questions about the FreeBSD GlusterFS port and build > > > > > > > > Hello Craig, Justin et all! > > > > Thank you for the provided link! I have tried to install it using the > > provided shar file; the build works, but 'make install fails' with > > the following error: > > > > > > > > " > > On make install: > > > > > > pkg-static: > > > lstat(/tmp/glusterfs/work/stage/usr/local/%%PYTHON_SITELIBDIR%%/gluster/): > > No such file or directory > > *** Error code 74 > > > > Stop. > > make: stopped in /tmp/glusterfs > > " > > > > > > Am I doing something wrong? or have I skipped / missed any steps? > > > > > > Thank you! > > > > > > Kind regards, > > Bogdan > > > > Hello Bogdan > > Just to clarify you are using the Commit candidate of GlusterFS port -- > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149791 > > and are you just running make install from the glusterfs directory ? > > The port should pull in Python as a build dependency. > > Kind Regards > > Craig Butler > > From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 19:32:09 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 983A4319 for ; Tue, 10 Feb 2015 19:32:09 +0000 (UTC) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E604B9B for ; Tue, 10 Feb 2015 19:32:08 +0000 (UTC) X-AuditID: 1209190f-f79546d000007593-a3-54da5cb16e4b Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id BE.94.30099.1BC5AD45; Tue, 10 Feb 2015 14:32:01 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id t1AJW0PS016686; Tue, 10 Feb 2015 14:32:01 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t1AJVwCG012222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 10 Feb 2015 14:32:00 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t1AJVw3K000970; Tue, 10 Feb 2015 14:31:58 -0500 (EST) Date: Tue, 10 Feb 2015 14:31:58 -0500 (EST) From: Benjamin Kaduk To: Sascha Frey Subject: Re: Unable to mount kerberized NFS share on Linux from FreeBSD 10.1 box In-Reply-To: <20150210080053.GA20995@TechFak.Uni-Bielefeld.DE> Message-ID: References: <20150209181747.GB9520@TechFak.Uni-Bielefeld.DE> <2131985962.2999032.1423524243651.JavaMail.root@uoguelph.ca> <20150210080053.GA20995@TechFak.Uni-Bielefeld.DE> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDIsWRmVeSWpSXmKPExsUixG6norsx5laIwdwOKYtjj3+yWWxtO8Tm wOQx49N8Fo8JB16xBTBFcdmkpOZklqUW6dslcGXM2lJSsFq84t783WwNjO+Fuhg5OSQETCRW rNnKBmGLSVy4tx7I5uIQEljMJPFvajMThLORUWL66hnsEM4hJol1jZ9ZIJwGRonHnycxdzFy cLAIaEvcP+oNMopNQEVi5puNYGNFBBQkTl1ZxwhSwiwgJXFnbQVIWFggSOLF2wssIDangJ3E 7nOtYOW8Ag4SR7/tYIUYv5pR4vy8J+wgCVEBHYnV+6ewQBQJSpyc+QTMZhbQklg+fRvLBEbB WUhSs5CkFjAyrWKUTcmt0s1NzMwpTk3WLU5OzMtLLdI10cvNLNFLTSndxAgKVE5J/h2M3w4q HWIU4GBU4uEtSLwZIsSaWFZcmXuIUZKDSUmUNzziVogQX1J+SmVGYnFGfFFpTmrxIUYJDmYl EV4VMaAcb0piZVVqUT5MSpqDRUmcd9MPvhAhgfTEktTs1NSC1CKYrAwHh5IE75FooEbBotT0 1Iq0zJwShDQTByfIcB6g4ZdBaniLCxJzizPTIfKnGBWlxHlbQBICIImM0jy4XlgiecUoDvSK MK8+SBUPMAnBdb8CGswENLig4AbI4JJEhJRUA+N88edvkvvU7IXr253525QLxbzrd//e2ZdZ svad68qiU5XrnRTc4rbMnW+aoy3xZEId/5xr89MNAhqXH7tt+UbxMserfa5/ZpeeudS188WH YHFzhoLF59xsJzpwRx2XupoYX2uwrGbSL6s3ETFunx/77c0KNjpsxcVj/+Sq7k7+taFHnovM lFFiKc5INNRiLipOBABtRAgM/wIAAA== Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 19:32:09 -0000 On Tue, 10 Feb 2015, Sascha Frey wrote: > Rick Macklem wrote: > > [...] > >> I found only one error message in /var/log/messages: > >> nfsd: can't register svc name > >> > >Well, this message indicates it isn't going to work. > >(This message means the nfsd couldn't register with the gssd daemon, > > so kerberized NFS won't work.) It is generated when the nfsd is > >started. > > > >The most common cause would be the gssd daemon not running when the > >nfsd daemon is started. If the gssd was running when the nfsd was started > >and this message is logged, there is a debug option on gssd that makes > >it chatty and that might indicate why it is failing. > > gssd was running before nfsd was started. > This message does not appear if nfsd starts without gssd running, > but it does appear as soon as gssd is started (if nfsd is already running). > > I started gssd in foreground mode (via gssd -d -v) > These messages appear when I start nfsd: > gssd_import_name: done major=0x0 minor=0 > gssd_acquire_cred: done major=0x70000 minor=0 > gssd_release_name: done major=0x0 minor=0 > gssd_import_name: done major=0x0 minor=0 > gssd_acquire_cred: done major=0x70000 minor=0 > gssd_release_name: done major=0x0 minor=0 > gssd_import_name: done major=0x0 minor=0 > gssd_acquire_cred: done major=0x70000 minor=0 > gssd_release_name: done major=0x0 minor=0 0x70000 is GSS_S_NO_CRED. Maybe you could truss or similar to find out what name it's trying to acquire credentials for? -Ben > No log output when trying to mount NFS share on the Linux machine. > > > I tried to mount it on the server itself. I'm able > to mount, but I can't access any files... > > [root@leonard ~]# mount -o sec=krb5 leonard.fs.cit-ec.net:/export/homes/sfrey /mnt > [root@leonard ~]# su - sfrey > [sfrey@leonard ~]$ kinit > sfrey@TECHFAK.UNI-BIELEFELD.DE's Password: > [sfrey@leonard ~]$ ls -lad /mnt > ls: /mnt: Permission denied > [sfrey@leonard ~]$ klist > Credentials cache: FILE:/tmp/krb5cc_21036 > Principal: sfrey@TECHFAK.UNI-BIELEFELD.DE > > Issued Expires Principal > Feb 10 08:54:31 2015 Feb 10 18:54:39 2015 krbtgt/TECHFAK.UNI-BIELEFELD.DE@TECHFAK.UNI-BIELEFELD.DE > Feb 10 08:54:36 2015 Feb 10 18:54:39 2015 nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > > > > >Also, there is this wiki. It is somewhat out of date, but I don't think > >anything has changed w.r.t. the server side. (I'm not sure what the > >current status is w.r.t. keytab entries encrypted in newer ways than > >des-cbc-crc is.) > >https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > I'll take a look into it. Maybe I missed something. > > > > > Cheers, > Sascha > _______________________________________________ > 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 Tue Feb 10 20:01:32 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46351CCF; Tue, 10 Feb 2015 20:01:32 +0000 (UTC) Received: from frv27.fwdcdn.com (frv158.fwdcdn.com [212.42.77.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06A5BED4; Tue, 10 Feb 2015 20:01:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Subject:To:From:Date; bh=BaqJtAEgOr91PIS1FSuMKTC/MmIoTE1PG57VUZ72oiA=; b=dc5uCdm+lA671i8QPbPDcEbUwzLZaf9LGGgjCLwBZSIvFqk5AUlAnYLf0AwO1suMGJBArNU/w++pkBPHzC3CXSvKW4ImGqQMiNE0YM/3oCIjWVPVbI2p1Ha+MExtYW1dRD7A6Q2uarAMNbfp0WspmasCovyOmeu3JgvMoNPtcJU=; Received: from [178.137.225.182] (helo=nonamehost.local) by frv27.fwdcdn.com with esmtpsa ID 1YLGzy-0008i0-1M ; Tue, 10 Feb 2015 22:01:30 +0200 Date: Tue, 10 Feb 2015 22:01:29 +0200 From: Ivan Klymenko To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: [ZFS] [panic] Fatal trap 12: page fault while in kernel mode. Message-ID: <20150210220129.3d780d50@nonamehost.local> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=178.137.225.182; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 20:01:32 -0000 I do not know the conditions - it just happened. http://pastebin.com/BASJB599 From owner-freebsd-fs@FreeBSD.ORG Tue Feb 10 23:33:44 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 20A547E7 for ; Tue, 10 Feb 2015 23:33:44 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id C96F5BA8 for ; Tue, 10 Feb 2015 23:33:43 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2ALBQCPlNpU/95baINbDoNKWgSCfcALCoUnSgKBYwEBAQEBAXyEDAEBAQMBAQEBICsgCwUWGAICDQcMBgIpAQkmBggHBAEcBIgECA26IYUtkSMBAQEBAQEBAQEBAQEBAQEBAQEBARiBIY4FAQEbNAcYglCBQgWKKohHgz6DbZEoIoMxWyAxAQaBBDl/AQEB X-IronPort-AV: E=Sophos;i="5.09,553,1418101200"; d="scan'208";a="191849185" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 10 Feb 2015 18:33:36 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 84F8CB3F0B; Tue, 10 Feb 2015 18:33:36 -0500 (EST) Date: Tue, 10 Feb 2015 18:33:36 -0500 (EST) From: Rick Macklem To: Benjamin Kaduk Message-ID: <1803458422.716795.1423611216530.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: Unable to mount kerberized NFS share on Linux from FreeBSD 10.1 box MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 23:33:44 -0000 Benjamin Kaduk wrote: > On Tue, 10 Feb 2015, Sascha Frey wrote: > > > Rick Macklem wrote: > > > > [...] > > >> I found only one error message in /var/log/messages: > > >> nfsd: can't register svc name > > >> > > >Well, this message indicates it isn't going to work. > > >(This message means the nfsd couldn't register with the gssd > > >daemon, > > > so kerberized NFS won't work.) It is generated when the nfsd is > > >started. > > > > > >The most common cause would be the gssd daemon not running when > > >the > > >nfsd daemon is started. If the gssd was running when the nfsd was > > >started > > >and this message is logged, there is a debug option on gssd that > > >makes > > >it chatty and that might indicate why it is failing. > > > > gssd was running before nfsd was started. > > This message does not appear if nfsd starts without gssd running, > > but it does appear as soon as gssd is started (if nfsd is already > > running). > > > > I started gssd in foreground mode (via gssd -d -v) > > These messages appear when I start nfsd: > > gssd_import_name: done major=0x0 minor=0 > > gssd_acquire_cred: done major=0x70000 minor=0 > > gssd_release_name: done major=0x0 minor=0 > > gssd_import_name: done major=0x0 minor=0 > > gssd_acquire_cred: done major=0x70000 minor=0 > > gssd_release_name: done major=0x0 minor=0 > > gssd_import_name: done major=0x0 minor=0 > > gssd_acquire_cred: done major=0x70000 minor=0 > > gssd_release_name: done major=0x0 minor=0 > > 0x70000 is GSS_S_NO_CRED. > Yea, unfortunately I think you'll find that this is the catch-all when you dig into the Heimdal library. (All the gssd does is take the upcalled arguments and do the call against the library. This is the reply the gss_acquire_cred() library call made. Why isn't it working? I have no idea. It is strange that "kinit -k ..." works, but this does not. One thing to check is to see if the keytab entry has multiple encryption types in it. If it does, you might want to re-create the keytab entry with only the default encryption type (as set in the NFS server's /etc/krb.conf). I have seen problems when the keytab entry has multiple encryption types, but I'm not sure what was broken. Another simple thing to check is "# hostname" and make sure it has "leonard.fs.cit-ec.net" and not "leonard", since it will use nfs@ as the host-based name and the must be the fully qualified domain name. > Maybe you could truss or similar to find out what name it's trying to > acquire credentials for? > It should be nfs@leonard.fs.cit-ec.net (or nfs/leonard.fs.cit-ec.net@ if written in the Kerberos mechanism's way). However, it can't hurt to check and if it isn't the above, that would explain why it isn't working. > -Ben > > > No log output when trying to mount NFS share on the Linux machine. > > > > > > I tried to mount it on the server itself. I'm able > > to mount, but I can't access any files... > > > > [root@leonard ~]# mount -o sec=krb5 > > leonard.fs.cit-ec.net:/export/homes/sfrey /mnt > > [root@leonard ~]# su - sfrey > > [sfrey@leonard ~]$ kinit > > sfrey@TECHFAK.UNI-BIELEFELD.DE's Password: > > [sfrey@leonard ~]$ ls -lad /mnt > > ls: /mnt: Permission denied Yea, the FreeBSD client (I didn't choose to code it this way) falls back to AUTH_SYS when Kerberos doesn't work. I suspect if you looked at a packet trace in wireshark, you'd see it trying AUTH_SYS for this. rick > > [sfrey@leonard ~]$ klist > > Credentials cache: FILE:/tmp/krb5cc_21036 > > Principal: sfrey@TECHFAK.UNI-BIELEFELD.DE > > > > Issued Expires Principal > > Feb 10 08:54:31 2015 Feb 10 18:54:39 2015 > > krbtgt/TECHFAK.UNI-BIELEFELD.DE@TECHFAK.UNI-BIELEFELD.DE > > Feb 10 08:54:36 2015 Feb 10 18:54:39 2015 > > nfs/leonard.fs.cit-ec.net@TECHFAK.UNI-BIELEFELD.DE > > > > > > > >Also, there is this wiki. It is somewhat out of date, but I don't > > >think > > >anything has changed w.r.t. the server side. (I'm not sure what > > >the > > >current status is w.r.t. keytab entries encrypted in newer ways > > >than > > >des-cbc-crc is.) > > >https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > > > I'll take a look into it. Maybe I missed something. > > > > > > > > > > Cheers, > > Sascha > > _______________________________________________ > > 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 Feb 11 16:23:18 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6238321D; Wed, 11 Feb 2015 16:23:18 +0000 (UTC) Received: from frv27.fwdcdn.com (frv158.fwdcdn.com [212.42.77.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 21334818; Wed, 11 Feb 2015 16:23:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:To:From:Date; bh=zkusk+1i3VhJvAlqt+Xk74QnFxW8Ulx4Xqo82xuSg1Y=; b=u15Cy+kilhOySltYSuR1i7PBNrzyzvnABC09zqeHmspP15vZtu3PM3ilSC/QHpUO2DL62l5HILkanSfG+75IwKrHTf8U2r3/Kr/m4KALng58Y3Uw9v7AHmWhOxBFnHT3bgTnLyh3AerHn81cxptpW4kM9VmW0In8Ot4wwFmMRqw=; Received: from [178.137.225.182] (helo=nonamehost.local) by frv27.fwdcdn.com with esmtpsa ID 1YLa4I-0008Um-GF ; Wed, 11 Feb 2015 18:23:14 +0200 Date: Wed, 11 Feb 2015 18:23:13 +0200 From: Ivan Klymenko To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: [ZFS] [panic] Fatal trap 12: page fault while in kernel mode. Message-ID: <20150211182313.5047a8b3@nonamehost.local> In-Reply-To: <20150210220129.3d780d50@nonamehost.local> References: <20150210220129.3d780d50@nonamehost.local> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Authentication-Result: IP=178.137.225.182; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 16:23:18 -0000 =D0=92 Tue, 10 Feb 2015 22:01:29 +0200 Ivan Klymenko =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > I do not know the conditions - it just happened. >=20 > http://pastebin.com/BASJB599 > _______________________________________________ > 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" http://pastebin.com/8HjebJKB http://pastebin.com/dx8PJKNr From owner-freebsd-fs@FreeBSD.ORG Thu Feb 12 10:35:35 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DC54E26E for ; Thu, 12 Feb 2015 10:35:35 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54F02CBD for ; Thu, 12 Feb 2015 10:35:35 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id b6so8656688lbj.2 for ; Thu, 12 Feb 2015 02:35:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb.com; s=google; h=date:from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; bh=yr2Ni5RVRmFkAouxbPc+9IGMej3uN3po12e/82gJrag=; b=Kymd5/oJFCQyyIhWNw5NXoV1d2UFmliDml4ZJdMhUrpMV/2ov1bJNS/kz+ruRMRrBj sQT+kDtpAIBCqRH8QHz/wD+aJzd+QqsHzwSz534WGKiMZeC/VZ/KjvrOmHoSEPps5Cqj Y2j7IX8c2ksgPyWxheUo15oEtVKENZOhv2nXk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-type:content-transfer-encoding; bh=yr2Ni5RVRmFkAouxbPc+9IGMej3uN3po12e/82gJrag=; b=H4gAPLx3YmbHUrDSwbQxmTkZsT5Vj9ri9PnbggHrvvoL2oHfxmp0PpnzQeu3rVnaUH iQdc4OvmFs1m5vvyIS35e/1Xok2warxTKQOSbsn/Z68PIKsuUCIYXWsDIJ2t2WgVG1cf bipEN03b+mBxBBLwghrmLjz4tGxkSW0nucvWrTTLbMDTpwsLgVIVZ5p/4ZrHoZfmEQgk bLua8VvT+UbOFN7z6gNc4squmqstrizeubRd4xA4JI8Rr8GgBn1fWn1bWumbwsqvoSlj usF/NQBw8ov42kxUBrehJvavRN8SF9b6y47DKsAyKNvSSUF9gBYjGq1APT+dNf8w2o4S +R9Q== X-Gm-Message-State: ALoCoQn7q/gugE4KwgRJ08220VtOJ5VnwpdQIyLjt2F63xrzNZCkucZwDSz2p7M2k1+ZLcGXNx6c X-Received: by 10.112.150.98 with SMTP id uh2mr2561650lbb.92.1423737333209; Thu, 12 Feb 2015 02:35:33 -0800 (PST) Received: from rsbsd.rsb ([31.200.12.40]) by mx.google.com with ESMTPSA id 5sm685546lam.33.2015.02.12.02.35.31 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Feb 2015 02:35:32 -0800 (PST) Date: Thu, 12 Feb 2015 12:35:29 +0200 From: Beeblebrox To: freebsd-fs@freebsd.org Subject: Several NFS errors on diskless clients Message-ID: <20150212123529.013d6a84@rsbsd.rsb> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 10:35:35 -0000 I have some errors I'm unable sort on my PXE-booting diskless clients. 1. ACL for NFS-V4 confuses jailed clients: Root for diskless clients is served from jail, which basically can only ser= ve dhcp and tftp. Since NFS can't be jailed, it is served from host. * It seems root cannot be mounted as V4 and is limited to V2. Thus the /etc= /exports file: {/data/amd64 -ro -network 192.168.2.0/26 # folder where jail resides V4: / /usr/local -ro -network 192.168.2.0/26 /home -network 192.168.2.0/26} * The client /etc folder is served from /data/amd64/conf/base/etc.cpio.gz, = and it is a copy of host /etc. * listing contents of mounted V4 folders (/home or /usr/local) shows a numb= er rather than user ID, but client etc/*pwd.db and etc/group are all exact = copies of what is on host. This causes user-ID problems for my setup. Is there a solution to this? 2. For de-bugging, I reverted all exports to V2/3. Then, (although I probab= ly don't need it) I do "service hald onestart" (dbus has already been start= ed) "nfs_getpages: error 13 vm_fault: pager read error, pid 652 (dbus-daemon-launch-) nfs_getpages: error 13 vm_fault: pager read error, pid 664 (dbus-daemon-launch-)" How significant is this error? 3. Client rc.conf setting is unable to start these services (not so on host= ): dbus_enable=3D"YES" distccd_enable=3D"YES" \ distccd_flags=3D"-a 192.168.2.1" Thanks and regards. --=20 FreeBSD_amd64_11-Current_RadeonKMS From owner-freebsd-fs@FreeBSD.ORG Thu Feb 12 10:58:42 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34286553 for ; Thu, 12 Feb 2015 10:58:42 +0000 (UTC) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E532EB6 for ; Thu, 12 Feb 2015 10:58:41 +0000 (UTC) Received: by mail-lb0-f170.google.com with SMTP id u14so8756870lbd.1 for ; Thu, 12 Feb 2015 02:58:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb.com; s=google; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=bNWvWgX8wNYV5wAsNd5Ky/XQGrZbcjQZMIoN3EhkjNs=; b=GweW9VtHxXhxzuPb7MqcDfu1eX3WlhH+LbThX0AirsIDDgyfQxpQrsXz6OZRbrdgaU W2gucq647xuVP2kAnYZ74f2azWKopon7tUdCzxYunV/cXO7DQExJMzU7d44JYyIFU9OA 39wCSH67665m802IjgRh13hXi5tfQC7PRC+OM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=bNWvWgX8wNYV5wAsNd5Ky/XQGrZbcjQZMIoN3EhkjNs=; b=ViF3KtgsJ14hEafW4pSuhiYobe6OVpmgKcnIIlILhEmw6J9a7qZgeH/Z+nnFPRrSPJ oy90Kv0UnEVVQeNFnfVM/r2Jo7UiqQ8DnQ4Z5BmrOMVy0iTvFqzIyj+1qAqGamNYs40R 7pDzBW/S5zaZzZ4WXD8B5zbYVWJw+n7aSb/kJ4aUs+UwIAe7D01nbzctD6f7G51I/g5T 1fqMySygzBllrRB/sTzgaATfpoOBzQ3ZHkPuhJRs/ugCiFAb2yndGOxJnWndT5I6PMEA Sw4azRu0eXz5tPa9Sk0ButdNgn4393cmXufgtGpSAvVWLiMiajVMNOYt+J9lmXA21jaS ltsw== X-Gm-Message-State: ALoCoQnFlh3aOoyN6inQ+WcbIn9jQ7Fy8zPx2D5oo43iwimnLkH5J4IYUwKOoambfaxVkpkAM8t6 X-Received: by 10.112.199.39 with SMTP id jh7mr2735604lbc.46.1423738719562; Thu, 12 Feb 2015 02:58:39 -0800 (PST) Received: from rsbsd.rsb ([31.200.12.40]) by mx.google.com with ESMTPSA id n3sm694845lbm.39.2015.02.12.02.58.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Feb 2015 02:58:38 -0800 (PST) Date: Thu, 12 Feb 2015 12:58:36 +0200 From: Beeblebrox To: freebsd-fs@freebsd.org Subject: Re: Several NFS errors on diskless clients Message-ID: <20150212125836.5013fa33@rsbsd.rsb> In-Reply-To: <20150212123529.013d6a84@rsbsd.rsb> References: <20150212123529.013d6a84@rsbsd.rsb> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 10:58:42 -0000 > 2. For de-bugging, I reverted all exports to V2/3. Then, (although I > probably don't need it) I do "service hald onestart" (dbus has > already been started) "nfs_getpages: error 13 vm_fault: pager read > error, pid 652 (dbus-daemon-launch-) nfs_getpages: error 13 > vm_fault: pager read error, pid 664 (dbus-daemon-launch-)" I'm now getting this error without starting HAL, when I try to login to a D= esktop session from Slim on a diskless client. The error prevents me from o= pening a Desktop session and X just hangs. No dbus, no desktop :( --=20 FreeBSD_amd64_11-Current_RadeonKMS From owner-freebsd-fs@FreeBSD.ORG Thu Feb 12 13:35:45 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBCCBA5D for ; Thu, 12 Feb 2015 13:35:45 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id B1F5F131 for ; Thu, 12 Feb 2015 13:35:45 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NJN00KFDVBLXV00@hades.sorbs.net> for freebsd-fs@freebsd.org; Thu, 12 Feb 2015 05:40:34 -0800 (PST) Message-id: <54DCAC29.8000301@sorbs.net> Date: Thu, 12 Feb 2015 14:35:37 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Mike Tancsa Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> <54D924DD.4000205@sorbs.net> In-reply-to: <54D924DD.4000205@sorbs.net> Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 13:35:45 -0000 Michelle Sullivan wrote: > > So far (few hours in) zfs import -fFX has not faulted with this image... > it's running out of memory currently about 16G of 32G- however 9.2-P15 > kernel died within minutes... out of memory (all 32G and swap) so am > more optimistic at the moment... Fingers Crossed. > And the answer: 11-STABLE on a USB stick. Remove the drive that was replacing the hotspare (ie the replacement drive for the one that initially died) zpool import -fFX storage zpool export storage reboot back to 9.x zpool import storage re-insert drive replacement drive. reboot -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@FreeBSD.ORG Thu Feb 12 17:36:04 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E2CA79E; Thu, 12 Feb 2015 17:36:04 +0000 (UTC) Received: from frv27.fwdcdn.com (frv158.fwdcdn.com [212.42.77.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F1ADF14A; Thu, 12 Feb 2015 17:36:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:To:From:Date; bh=wdT1fxPSOe1GvcB3OXlAPpe49gyM+f5go5u3rlzgGRk=; b=AABYVFTqBv6syF//qJo3PUk/DNQGYQO3xHT1VG9nn2RnXd8dOwqnbxX3eccLVf17AR7snfqkNiCtBFaMWK63m4HOxwFQsrOs5WOxFLVSGz5czjlIx67OywhRyPllg53wzES/h447WBWhkl4NEtYPSWwSYeuetZRSNUcieyLWlbg=; Received: from [178.137.225.182] (helo=nonamehost.local) by frv27.fwdcdn.com with esmtpsa ID 1YLxg8-0007Cw-9s ; Thu, 12 Feb 2015 19:35:52 +0200 Date: Thu, 12 Feb 2015 19:35:46 +0200 From: Ivan Klymenko To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: [ZFS] [panic] Fatal trap 12: page fault while in kernel mode. Message-ID: <20150212193546.3d62c88b@nonamehost.local> In-Reply-To: <20150210220129.3d780d50@nonamehost.local> References: <20150210220129.3d780d50@nonamehost.local> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Authentication-Result: IP=178.137.225.182; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 17:36:04 -0000 =D0=92 Tue, 10 Feb 2015 22:01:29 +0200 Ivan Klymenko =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > I do not know the conditions - it just happened. >=20 > http://pastebin.com/BASJB599 next http://pastebin.com/hY8GYpjd From owner-freebsd-fs@FreeBSD.ORG Thu Feb 12 21:33:52 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D00A1A89 for ; Thu, 12 Feb 2015 21:33:52 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B6073F20 for ; Thu, 12 Feb 2015 21:33:52 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1CLXqdZ013651 for ; Thu, 12 Feb 2015 21:33:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 187261] [fusefs] FUSE kernel panic when using socket / bind Date: Thu, 12 Feb 2015 21:33:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: henry.hu.sh@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 21:33:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187261 Henry Hu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |henry.hu.sh@gmail.com --- Comment #3 from Henry Hu --- I've submitted bug 195000 which seems to be closely related to this bug, and I've provided a temporary fix. Please try that patch and check if it works. It's triggered through rsync, but it's also related to socket, and it also crashes in fuse_vnop_create. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Thu Feb 12 23:52:07 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 529E1134 for ; Thu, 12 Feb 2015 23:52:07 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 00117FCD for ; Thu, 12 Feb 2015 23:52:06 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DoBAC+O91U/95baINRCoNYWgSCfsAdCoUnSgKBaAEBAQEBAXyEDAEBAQMBAQEBIAQnIAsFFhgCAg0FFAIpAQkmBggHBAEaAgSIBAgNvhaXMAEBAQEBAQEDAQEBAQEBAQEagSGJa4QRBAcBARs0BxIMgkqBQgWKMIhPgz6DNziFF4wZIoICHIFuIDEHewkXIn8BAQE X-IronPort-AV: E=Sophos;i="5.09,567,1418101200"; d="scan'208";a="192311127" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 12 Feb 2015 18:51:59 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9928EB3EFE; Thu, 12 Feb 2015 18:51:59 -0500 (EST) Date: Thu, 12 Feb 2015 18:51:59 -0500 (EST) From: Rick Macklem To: Beeblebrox Message-ID: <1233670915.2450301.1423785119612.JavaMail.root@uoguelph.ca> In-Reply-To: <20150212123529.013d6a84@rsbsd.rsb> Subject: Re: Several NFS errors on diskless clients MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 23:52:07 -0000 Beeblebrox wrote: > I have some errors I'm unable sort on my PXE-booting diskless > clients. > > 1. ACL for NFS-V4 confuses jailed clients: > Root for diskless clients is served from jail, which basically can > only serve dhcp and tftp. Since NFS can't be jailed, it is served > from host. > * It seems root cannot be mounted as V4 and is limited to V2. Thus > the /etc/exports file: > {/data/amd64 -ro -network 192.168.2.0/26 # folder where jail resides > V4: / > /usr/local -ro -network 192.168.2.0/26 > /home -network 192.168.2.0/26} > * The client /etc folder is served from > /data/amd64/conf/base/etc.cpio.gz, and it is a copy of host /etc. > * listing contents of mounted V4 folders (/home or /usr/local) shows > a number rather than user ID, but client etc/*pwd.db and etc/group > are all exact copies of what is on host. This causes user-ID > problems for my setup. > Is there a solution to this? > Nope, a diskless root fs is not supported by NFSv4. There are a couple of reasons: 1 - The root fs can't map between uid/gid#s<->user/group names. Recent changes to NFSv4 does allow a uid/gid# in the owner/owner_group string. As such, I think this can work if the server has: vfs.nfsd.enable_stringtouid=1 and nfsuserd not running, such that only uid/gid#s are in the strings. 2 - The client needs a unique uuid string to identify the client uniquely. (That uuid won't be available when the client first boots.) I don't know a good solution for this. (Basically the client must have a unique identifier string. A simplistic implementation using something like the MAC and IP address of the client's network interface (the one used to get to the NFS server) might work? 3 - The client needs a file handle for the root dir. For some servers, including FreeBSD's, it is the same as the NFSv3 file handle. However, if it isn't the same, none of the boot code, which does NFSv2 or NFSv3 knows how to get it. --> Until these are resolved, a diskless NFSv4 root fs isn't going to work. > 2. For de-bugging, I reverted all exports to V2/3. Then, (although I > probably don't need it) I do "service hald onestart" (dbus has > already been started) > "nfs_getpages: error 13 > vm_fault: pager read error, pid 652 (dbus-daemon-launch-) > nfs_getpages: error 13 > vm_fault: pager read error, pid 664 (dbus-daemon-launch-)" > How significant is this error? > For some reason, it can't page the file in, so I'd assume that executable isn't going to work. 13 is EACCES, so the client read of this is failing, due to an access error. One possibility would be that the pagein is being done by root and that is being mapped to "nobody" and failing, due to lack of world read/execute permission on the file. Try adding -maproot=root to the export line on the server for this file system or maybe adding r-x for world to the file's mode might fix it. Without looking at the packet trace, it is hard to guess what uid the client would be using to do the page-in. (root maybe?) rick > 3. Client rc.conf setting is unable to start these services (not so > on host): > dbus_enable="YES" > distccd_enable="YES" \ distccd_flags="-a 192.168.2.1" > > Thanks and regards. > > -- > FreeBSD_amd64_11-Current_RadeonKMS > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@FreeBSD.ORG Fri Feb 13 12:25:28 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A982ABFE for ; Fri, 13 Feb 2015 12:25:28 +0000 (UTC) Received: from mail-la0-f51.google.com (mail-la0-f51.google.com [209.85.215.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 296198E5 for ; Fri, 13 Feb 2015 12:25:27 +0000 (UTC) Received: by labhz20 with SMTP id hz20so15909465lab.0 for ; Fri, 13 Feb 2015 04:25:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb.com; s=google; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=nvvRPcxP8D7csZf4SUxuHuCn3U26WvggmlcsXkKJzXQ=; b=H/UirSAhm7IUkt+zbRTBaLECpX8vgM5qsfrt/YjuMQmGwKuDZfDM2qqtp4envEfKoD ftU/qjOSnuxu9tgkqo/mlEf8TeagrhpHrjCJJ7WEO6WBZMrlehE/+WDZRc+rgfbVOIHf +VfZQOSGsfA78G5XP4o1e7kIlUbEFcOP/JPNk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=nvvRPcxP8D7csZf4SUxuHuCn3U26WvggmlcsXkKJzXQ=; b=SFca45QyyXl/ewgyV8nktmhdMMwenkGhAyCoirFmNhsxbMIjfcXPfg6X6W/HpVyiYc zXcZgWFFrzS7abvJKX8TGwijcinCiQ98ehVlzDeQ8ypWltNm+xhmaMdW6928Bzd/uziO ZvFMIRWuq28d7cqGXfda1C/0nCEMdPEHPF4vzwoWzCsLVTOMJknkXZGmAKIe9UKeDvBz X0ziBe9UikZweH3S/14Uay+lfWAGeddw9JnI1WNE6UR85r/Gjnoycco7crpKtMs3Hewg pXBg66vhPEZ5Nc3QIxIcawc1B4tgWcBaWU5VxJ3oLYeOjczI9FfIfs9S7SBUOH9FP8cX 4+gw== X-Gm-Message-State: ALoCoQnbPVg1hGyrPtepX3Zmn03oyxyT9OXD6qIqoKn9vRbeHY2xaJIxmMOvo1TVlTDY2w9HYa3/ X-Received: by 10.152.18.225 with SMTP id z1mr7905895lad.124.1423830319879; Fri, 13 Feb 2015 04:25:19 -0800 (PST) Received: from rsbsd.rsb ([31.200.20.192]) by mx.google.com with ESMTPSA id v5sm1349705lby.9.2015.02.13.04.25.18 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Feb 2015 04:25:19 -0800 (PST) Date: Fri, 13 Feb 2015 14:25:16 +0200 From: Beeblebrox To: Rick Macklem Subject: Re: Several NFS errors on diskless clients Message-ID: <20150213142516.569ecc44@rsbsd.rsb> In-Reply-To: <1233670915.2450301.1423785119612.JavaMail.root@uoguelph.ca> References: <20150212123529.013d6a84@rsbsd.rsb> <1233670915.2450301.1423785119612.JavaMail.root@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2015 12:25:28 -0000 Hi Rick, thanks for answering, but it seems there's a slight mis-understand= ing. * I have 3 NFS exports, mount version on client confirmed with "nfsstat -m": V2: /data/amd64, mounts to root as ro V4: /usr/local, mounts to same as ro V4: /home, mounts to same as rw * Root is being mounted as V2, not a problem for me. However, when I "ls -l= a" /home or /usr/local (the V4 mounts), I see file ownership problem (numbe= rs instead of actual user name). This is true for folders owned ANY user (r= oot, me, etc): drwxr-xr-x 106 32767 32767 date-time folder-name (always the same nu= mber 32767) * I turned on some debugging with "nfsuserd -verbose" and I can see: added uid=3D0 name=3Droot \ added gid=3D0 name=3Droot added uid=3D1001 name=3Dme \ added gid=3D1001 name=3Dme added uid=3D350 name=3D_sabnzbd \ added gid=3D350 name=3D_sabnzbd * Most Likely reason: The NFS-V2 export (client root /data/amd64 folder) is= at the same time a Jail. This probably causes "some process number in the = jail" not matching up with process number on Host, thus the failure to assi= gn proper name to file ownership. My /etc/jail.conf: pxe { name =3D pxe; path =3D /data/amd64; ip4.addr =3D 192.168.2.1; #subnet as /32 breaks tftp host.hostname =3D pxe.me; devfs_ruleset =3D 12; allow.raw_sockets; mount.devfs; mount.fstab =3D /etc/fstab.pxe; } * I start the diskless client system with below script. Any additional pxe = service (dhcp, tftp, etc) is defined in /data/amd64/etc/rc.conf. jail -c pxe rpcbind -s -h 192.168.2.1 mountd -rnl -h 192.168.2.1 nfsd -ut -n 4 -h 192.168.2.1 nfsuserd -verbose * Starting dbus/hald on client while nfsuserd is running results in: a) added gid=3D556 name=3Dmessagebus \ added gid=3D562 name=3Dpolkit b) No message about "nfs_getpages: error 13" * If I don't run nfsuserd, or if I use NFS V2/3 for the /usr/local export: a) File permissions on the non-root exports get displayed by name. b) I see the "nfs_getpages: error 13" message. * I did not try the "-maproot=3Droot" solution, because it does not address= the problem of regular users (ie me) having incorrect file ownership under= /home/me. * File ownership under /var/run is correct because it's not NFS (it's MD) I hope I was better able to explain the issue this time. Regards. --=20 FreeBSD_amd64_11-Current_RadeonKMS From owner-freebsd-fs@FreeBSD.ORG Fri Feb 13 20:18:48 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72FC2C16 for ; Fri, 13 Feb 2015 20:18:48 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 58A8B3A5 for ; Fri, 13 Feb 2015 20:18:48 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1DKImXm074401 for ; Fri, 13 Feb 2015 20:18:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 191895] [ext2fs] [panic] ext2_dirbad: /mnt: bad dir ino 32787 at offset 6136: mangled entry Date: Fri, 13 Feb 2015 20:18:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pfg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2015 20:18:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191895 --- Comment #5 from Pedro F. Giffuni --- Hi again Peter; FWIW, Coverity found an issue that was fixed recently (r275645) and already MFC'd. It would be great if you can verify if the problem is still there. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Fri Feb 13 21:30:17 2015 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0EADDC4B for ; Fri, 13 Feb 2015 21:30:17 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E3E3ED2A for ; Fri, 13 Feb 2015 21:30:16 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1DLUGme099628 for ; Fri, 13 Feb 2015 21:30:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 191895] [ext2fs] [panic] ext2_dirbad: /mnt: bad dir ino 32787 at offset 6136: mangled entry Date: Fri, 13 Feb 2015 21:30:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pho@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2015 21:30:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191895 --- Comment #6 from Peter Holm --- No change: FreeBSD t2.osted.lan 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r278708: Fri Feb 13 22:06:30 CET 2015 pho@t2.osted.lan:/usr/src/sys/amd64/compile/PHO amd64 root@t2:~pho/stress2/misc # ./ext2fs.sh mke2fs 1.42.10 (18-May-2014) run: run time 0+00:10:00, incarnations 1, load 100, verbose 1 22:26:49 Loop #1 lockf2: run time 0+00:02:00, incarnations 19, load 80, verbose 1 symlink: run time 0+00:02:00, incarnations 1, load 80, verbose 1 rw: run time 0+00:02:00, incarnations 1, load 80, verbose 1 fts: run time 0+00:02:00, incarnations 10, load 80, verbose 1 link: run time 0+00:02:00, incarnations 13, load 80, verbose 1 openat: run time 0+00:02:00, incarnations 1, load 80, verbose 1 lockf: run time 0+00:02:00, incarnations 1, load 80, verbose 1 rename: run time 0+00:02:00, incarnations 17, load 80, verbose 1 mkfifo: run time 0+00:02:00, incarnations 17, load 80, verbose 1 creat: run time 0+00:02:00, incarnations 15, load 80, verbose 1 mkdir: run time 0+00:02:00, incarnations 17, load 80, verbose 1 bad directory entry: rec_len is smaller than minimal offset=2040, inode=0, rec_len=8, name_len=0 panic: ext2_dirbad: /mnt: bad dir ino 49187 at offset 6136: mangled entry cpuid = 17 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe081e1a8130 vpanic() at vpanic+0x189/frame 0xfffffe081e1a81b0 panic() at panic+0x43/frame 0xfffffe081e1a8210 ext2_search_dirblock() at ext2_search_dirblock+0x2a3/frame 0xfffffe081e1a8290 ext2_htree_lookup() at ext2_htree_lookup+0x162/frame 0xfffffe081e1a8390 ext2_lookup_ino() at ext2_lookup_ino+0x20c/frame 0xfffffe081e1a84b0 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0x10f/frame 0xfffffe081e1a84e0 vfs_cache_lookup() at vfs_cache_lookup+0xd6/frame 0xfffffe081e1a8540 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x10f/frame 0xfffffe081e1a8570 lookup() at lookup+0x5d5/frame 0xfffffe081e1a8600 namei() at namei+0x536/frame 0xfffffe081e1a86c0 vn_open_cred() at vn_open_cred+0xd5/frame 0xfffffe081e1a8820 kern_openat() at kern_openat+0x257/frame 0xfffffe081e1a89a0 amd64_syscall() at amd64_syscall+0x29c/frame 0xfffffe081e1a8ab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe081e1a8ab0 --- syscall (499, FreeBSD ELF64, sys_openat), rip = 0x800b08fba, rsp = 0x7fffffffe5b8, rbp = 0x7fffffffe690 --- KDB: enter: panic [ thread pid 970 tid 100491 ] Stopped at kdb_enter+0x3e: movq $0,kdb_why db> -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Sat Feb 14 02:01:25 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65C34834 for ; Sat, 14 Feb 2015 02:01:25 +0000 (UTC) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id E69C3BC8 for ; Sat, 14 Feb 2015 02:01:23 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DlBAD7q95U/95baINbhDaCf8JRgk8CgVQBAQEBAQF8hAwBAQEDASMEIDIFFhgCAg0FFAJZBi6ICgi9UYUWkWYBAQEBAQEBAwEBAQEBAQEBARmBIYlrhDk0BxINgkmBQgWKN49KhVCMHSKCAhyBbiCBPDl/AQEB X-IronPort-AV: E=Sophos;i="5.09,574,1418101200"; d="scan'208";a="190739809" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 13 Feb 2015 21:00:52 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 569AEB4172; Fri, 13 Feb 2015 21:00:52 -0500 (EST) Date: Fri, 13 Feb 2015 21:00:52 -0500 (EST) From: Rick Macklem To: Beeblebrox Message-ID: <1957238464.3335859.1423879252335.JavaMail.root@uoguelph.ca> In-Reply-To: <20150213142516.569ecc44@rsbsd.rsb> Subject: Re: Several NFS errors on diskless clients MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2015 02:01:25 -0000 Beeblebrox wrote: > Hi Rick, thanks for answering, but it seems there's a slight > mis-understanding. > > * I have 3 NFS exports, mount version on client confirmed with > "nfsstat -m": > V2: /data/amd64, mounts to root as ro > V4: /usr/local, mounts to same as ro > V4: /home, mounts to same as rw > > * Root is being mounted as V2, not a problem for me. However, when I > "ls -la" /home or /usr/local (the V4 mounts), I see file ownership > problem (numbers instead of actual user name). This is true for > folders owned ANY user (root, me, etc): > drwxr-xr-x 106 32767 32767 date-time folder-name (always the > same number 32767) > > * I turned on some debugging with "nfsuserd -verbose" and I can see: > added uid=0 name=root \ added gid=0 name=root > added uid=1001 name=me \ added gid=1001 name=me > added uid=350 name=_sabnzbd \ added gid=350 name=_sabnzbd > > * Most Likely reason: The NFS-V2 export (client root /data/amd64 > folder) is at the same time a Jail. This probably causes "some > process number in the jail" not matching up with process number on > Host, thus the failure to assign proper name to file ownership. My > /etc/jail.conf: > pxe { name = pxe; > path = /data/amd64; > ip4.addr = 192.168.2.1; #subnet as /32 breaks tftp > host.hostname = pxe.me; > devfs_ruleset = 12; > allow.raw_sockets; > mount.devfs; > mount.fstab = /etc/fstab.pxe; } > > * I start the diskless client system with below script. Any > additional pxe service (dhcp, tftp, etc) is defined in > /data/amd64/etc/rc.conf. > jail -c pxe > rpcbind -s -h 192.168.2.1 > mountd -rnl -h 192.168.2.1 > nfsd -ut -n 4 -h 192.168.2.1 > nfsuserd -verbose > Well, I have no idea what effect a jail would have (never used one), but since it appears that nfsuserd is resolving numbers to names... The owner and owner_group name in NFSv4 looks like: @ Since the "user-or-group" part seems to be working, then maybe the part isn't the same? (It doesn't really matter what it is, so long as it is the same for the server and client.) The "-domain" command line option on nfsuserd allows you to set it to whatever you want. (Without that option, it should be the dns-domain part of the client/server's fully qualified hostname.) However, what you write below suggests that the mapping is working, so I don't understand what is going on. > * Starting dbus/hald on client while nfsuserd is running results in: > a) added gid=556 name=messagebus \ added gid=562 name=polkit > b) No message about "nfs_getpages: error 13" > Well, the AUTH_SYS authenticator has the uid/gid-list for the process that is doing the nfs_getpages read. This uid/gid-list is used by the server to determine if EACCES is returned. It has nothing to do with nfsuserd, which only affects what the owner and owner_group strings are. (These strings are only is getattr and setattr operations.) Maybe this application does a Setattr (chown, chgrp...) on the file and that would work for NFSv4 if the mapping stuff is working. (But it doesn't seem to be, given the above.) > * If I don't run nfsuserd, or if I use NFS V2/3 for the /usr/local > export: > a) File permissions on the non-root exports get displayed by name. Without nfsuserd, the server will put the uid/gid# in the string and a fairly recent client will understand that for NFSv4. For NFSv2/3, the uid/gid#s are always used. > b) I see the "nfs_getpages: error 13" message. > I can think of a couple of explanations for this: 1 - The user/group database isn't consistent between client and server (ie. missing and/or different #s). 2 - Some other thread is doing the nfs_getpages() and using a different uid than the process. (I can't think of how this would happen for pageins, although I think it can happen for pageouts.) --> Looking at the packets in wireshark will tell you what is actually going on. Just in case you didn't already know, if you are going to use NFSv4 over AUTH_SYS, the clients and server need consistent user and group databases. Same names and same numbers. rick > * I did not try the "-maproot=root" solution, because it does not > address the problem of regular users (ie me) having incorrect file > ownership under /home/me. > > * File ownership under /var/run is correct because it's not NFS (it's > MD) > > I hope I was better able to explain the issue this time. > Regards. > -- > FreeBSD_amd64_11-Current_RadeonKMS > From owner-freebsd-fs@FreeBSD.ORG Sat Feb 14 12:53:17 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19324B1B for ; Sat, 14 Feb 2015 12:53:17 +0000 (UTC) Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C3BAD46 for ; Sat, 14 Feb 2015 12:53:16 +0000 (UTC) Received: by labhs14 with SMTP id hs14so20615898lab.1 for ; Sat, 14 Feb 2015 04:53:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb.com; s=google; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=DU4H4JVLOw1pNhpi/teGugDS6IjSRolSc4tAIWfzcSg=; b=Ny3sZ8PD4IePwa7Wdd1wDRi6vWONPBoot56vc19NQndazDjrGDS1DsEK8UDrh6fFRz EB0RYCk99vsaNgK/ThY36IvSPFeofSo246YvqyNRBsDpN0zcY1LAUUK1rErtyuKwxe/6 d8h3OHkqhN56x38OM+zbE/iDisLEfXKLVHL8Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=DU4H4JVLOw1pNhpi/teGugDS6IjSRolSc4tAIWfzcSg=; b=f3GyqkhIaLKtukJibMQxrzmF5dgDdVB/6JIKQTYWpM6XQnB00rFR889aS1+rpArpJS v9+eUkWv3H2BoJ8VVciuFclSuqRlLPOov4SYo09qxIimHvVWbMs0WmA+y/8J34CGHAFu tYD4dulHbxOy8q5xG4DLM5gm4xSrz7p9xYm2YOrFzoA+Rl0EoQdNXxUWGOQ9MvjkLruu sN4SObfvBxnlfJ22TuFMHSs2FkwxFpB6WBPS+6Uiv02Zlu6YmnFz7chAb+JBr41PeUMo JzSxIS8bDFqDMY8402ARlFKjnpnIUrFOixWEXGCkHgDNO/ByTUOMbLEckvNWuitlFPlF srZQ== X-Gm-Message-State: ALoCoQlr1EU0NARrk7jRhSwpiSbA8dvVXQzu7Op4VI+4xUBdH+dk2z9ebpcceJ/xmLqxsPKVHtKj X-Received: by 10.112.92.204 with SMTP id co12mr12534614lbb.43.1423918393920; Sat, 14 Feb 2015 04:53:13 -0800 (PST) Received: from rsbsd.rsb ([31.200.16.102]) by mx.google.com with ESMTPSA id r3sm1890411lal.16.2015.02.14.04.53.11 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Feb 2015 04:53:12 -0800 (PST) Date: Sat, 14 Feb 2015 14:53:09 +0200 From: Beeblebrox To: freebsd-fs@freebsd.org Subject: Re: Several NFS errors on diskless clients Message-ID: <20150214145309.38238df2@rsbsd.rsb> In-Reply-To: <1957238464.3335859.1423879252335.JavaMail.root@uoguelph.ca> References: <20150213142516.569ecc44@rsbsd.rsb> <1957238464.3335859.1423879252335.JavaMail.root@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2015 12:53:17 -0000 Hi, Rick. > Just in case you didn't already know, if you are going to use NFSv4 > over AUTH_SYS, the clients and server need consistent user and group > databases. Same names and same numbers. I was aware of that, yet apparently missed a crucial step. There was a mis-= match between the /etc of host vs jail and I was missing several users/grou= ps. Corrected. > Since the "user-or-group" part seems to be working, then maybe the > part isn't the same? (It doesn't really matter what it > is, so long as it is the same for the server and client.) That, I was not aware of. I modified diskless client rc.conf to have "nfsus= erd_flags -domain same.name", and start nfsuserd with same.name from host. I was fortunate to see a solution to my problem #3 on the mail list BTW, se= rvices under NFS not starting, in client rc.conf: early_late_divider=3D"mou= ntcritremote". Services now start. The bulk of the oddities I could not figure out have been cleared by the ab= ove mentioned corrections. The only remaining problem is the "pager read er= ror". IDK how serious that is but the same error occurs if I try to start G= DM on the client, so it seems I need to get to the bottom of that as well: Client boots normally, nfsuserd running on both host + client, dbus already= started.=20 pcap file with "tcpdump -s 1500" for invoking on client "service hald onest= art" being PM'ed. Thanks for the help and Regards. From owner-freebsd-fs@FreeBSD.ORG Sat Feb 14 14:19:03 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44C6EB47 for ; Sat, 14 Feb 2015 14:19:03 +0000 (UTC) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C70D266C for ; Sat, 14 Feb 2015 14:19:02 +0000 (UTC) Received: from [78.35.157.235] (helo=fabiankeil.de) by smtprelay02.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YMdYg-000536-W0 for freebsd-fs@freebsd.org; Sat, 14 Feb 2015 15:18:59 +0100 Date: Sat, 14 Feb 2015 15:19:07 +0100 From: Fabian Keil To: freebsd-fs@freebsd.org Subject: Re: panic: solaris assert: rt->rt_space == 0 (0xe000 == 0x0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/range_tree.c, line: 153 Message-ID: <580853d0.0ab6eb7d@fabiankeil.de> In-Reply-To: <04f3092d.6fdfad8a@fabiankeil.de> References: <04f3092d.6fdfad8a@fabiankeil.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/VrTK.JS8LJI6ASPZZ6VTbyh"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2015 14:19:03 -0000 --Sig_/VrTK.JS8LJI6ASPZZ6VTbyh Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Fabian Keil wrote: > Using an 11.0-CURRENT based on r276255 I just got a panic > after trying to export a certain ZFS pool: [...] > #10 0xffffffff81bdd22f in assfail3 (a=3D, lv=3D, op=3D, rv=3D, f= =3D, l=3D) > at /usr/src/sys/cddl/compat/opensolaris/kern/opensolaris_cmn_err.c:91 > #11 0xffffffff8194afc4 in range_tree_destroy (rt=3D0xfffff80011586000) at= /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/range_tree.c:153 > #12 0xffffffff819488bc in metaslab_fini (msp=3D0xfffff800611a9800) at /us= r/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/metaslab.c:1398 > #13 0xffffffff81965841 in vdev_free (vd=3D0xfffff8000696d800) at /usr/src= /sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c:994 > #14 0xffffffff819657e1 in vdev_free (vd=3D0xfffff80040532000) at /usr/src= /sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c:683 > #15 0xffffffff81953948 in spa_unload (spa=3D0xfffff800106af000) at /usr/s= rc/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c:1314 > #16 0xffffffff81957a58 in spa_export_common (pool=3D= , new_state=3D1, oldconfig=3D0x0, force=3D, hardforce= =3D0) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c:4540 > #17 0xffffffff81957b08 in spa_export (pool=3D0x0, oldconfig=3D0xfffffe009= 4a624f0, force=3D128, hardforce=3D50) at /usr/src/sys/cddl/contrib/opensola= ris/uts/common/fs/zfs/spa.c:4574 > #18 0xffffffff8199ed50 in zfs_ioc_pool_export (zc=3D0xfffffe0006fbf000) a= t /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:1618 [...] > (kgdb) f 11 > #11 0xffffffff8194afc4 in range_tree_destroy (rt=3D0xfffff80011586000) at= /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/range_tree.c:153 > 153 VERIFY0(rt->rt_space); [...] >=20 > After rebooting and reimporting the pool it looked like this: >=20 > fk@r500 ~ $sudo zpool status -v wde4 > pool: wde4 > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://illumos.org/msg/ZFS-8000-8A > scan: scrub canceled on Tue Jan 20 00:22:26 2015 > config: >=20 > NAME STATE READ WRITE CKSUM > wde4 ONLINE 0 0 19 > label/wde4.eli ONLINE 0 0 76 >=20 > errors: Permanent errors have been detected in the following files: >=20 > <0xaf11f>:<0x0> > wde4/backup/r500/tank/home/fk:<0x0> > <0xffffffffffffffff>:<0x0> >=20 > The export triggered the same panic again, but with a different rt->rt_sp= ace value: >=20 > panic: solaris assert: rt->rt_space =3D=3D 0 (0x22800 =3D=3D 0x0), file: = /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/range_tree.c, line:= 153 >=20 > I probably won't have time to scrub the pool and investigate this further > until next week. With this patch and vfs.zfs.recover=3D1 the pool can be exported without pa= nic: https://www.fabiankeil.de/sourcecode/electrobsd/range_tree_destroy-Optional= ly-tolerate-non-zero-rt-r.diff Warnings from three pool exports: Feb 14 13:49:22 r500 kernel: [268] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 12000 Feb 14 13:49:22 r500 kernel: [268] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2e200 Feb 14 13:49:22 r500 kernel: [268] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 12000 Feb 14 13:49:22 r500 kernel: [268] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2e200 Feb 14 13:49:22 r500 kernel: [268] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 12000 Feb 14 13:49:22 r500 kernel: [268] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2e200 Feb 14 13:50:25 r500 kernel: [331] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 11200 Feb 14 13:50:25 r500 kernel: [331] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2ea00 Feb 14 13:50:25 r500 kernel: [331] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 11200 Feb 14 13:50:25 r500 kernel: [331] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2ea00 Feb 14 13:50:25 r500 kernel: [331] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 11200 Feb 14 13:50:25 r500 kernel: [331] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2ea00 Feb 14 13:52:27 r500 kernel: [453] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 12600 Feb 14 13:52:27 r500 kernel: [453] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2ea00 Feb 14 13:52:27 r500 kernel: [453] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 12600 Feb 14 13:52:27 r500 kernel: [453] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2ea00 Feb 14 13:52:27 r500 kernel: [453] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 12600 Feb 14 13:52:27 r500 kernel: [453] Solaris: WARNING: zfs: range_tree_destro= y(): rt->rt_space !=3D 0: 2ea00 My impression is that the messages are the result of metaslab_fini() trigge= ring the problem tree times per export for each tree in msp->ms_defertree. If the pool is imported readonly, the problem isn't triggered. Due to interruptions the scrubbing will probably take a couple of days. ZFS continues to complain about checksum errors but apparently no affected files have been found yet: fk@r500 ~ $sudo zpool status -v wde4=20 pool: wde4 state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: scrub in progress since Sat Feb 14 14:19:15 2015 32.0G scanned out of 1.68T at 10.8M/s, 44h25m to go 0 repaired, 1.86% done config: NAME STATE READ WRITE CKSUM wde4 ONLINE 0 0 867 label/wde4.eli ONLINE 0 0 3.39K errors: Permanent errors have been detected in the following files: <0xaf11f>:<0x0> wde4/backup/r500/tank/home/fk:<0x0> <0xffffffffffffffff>:<0x0> BTW, any opinions on allowing to change vfs.zfs.recover without reboot? https://www.fabiankeil.de/sourcecode/electrobsd/Make-vfs.zfs.recover-writab= le-after-boot.diff Fabian --Sig_/VrTK.JS8LJI6ASPZZ6VTbyh Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTfWVsACgkQBYqIVf93VJ2a2QCeLmVs+d3KcJori1RVobhq6qq9 jBEAn2V2c2+tct25EnZvZCdx5e05/Bcj =6xwY -----END PGP SIGNATURE----- --Sig_/VrTK.JS8LJI6ASPZZ6VTbyh--