From owner-freebsd-fs@FreeBSD.ORG Sun Jul 12 07:06:15 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23E8D106564A for ; Sun, 12 Jul 2009 07:06:15 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from smtp106.biz.mail.mud.yahoo.com (smtp106.biz.mail.mud.yahoo.com [68.142.200.254]) by mx1.freebsd.org (Postfix) with SMTP id D706D8FC1B for ; Sun, 12 Jul 2009 07:06:14 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 24724 invoked from network); 12 Jul 2009 07:06:14 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@96.35.144.62 with login) by smtp106.biz.mail.mud.yahoo.com with SMTP; 12 Jul 2009 07:06:14 -0000 X-Yahoo-SMTP: lf_ydH2swBBBfU4zSj6s29Gn1AqWpQIrFClaJdTnJv1EdZ8- X-YMail-OSG: EiVBy00VM1mxlMPWLr6pKxHD914d6miJQy5knqKJL3jNz_FpUn2rGXp9j7YkM5Yg_jZGKuaYGDEIueDHpwJ99gB9vUip6gp2Aj3vMOR7oifJMgdqjuRpmsrkCpPHD1VjqA4L4XlXI_aOvj4mgl_6pz_KCOXGxgM.cI0UOm6IP4xoNeoVbNF08eUub8qNPGJORQh1c.znYSUZMsibdmjNPbO2oajv6b2RCXZaYgwzQ9wO89kIwyl09_ciWf6sF4AovCkx8hoq5oZQI92wUIJSLIE5e.5KvLUKL8aINVy2hHGzV06Lawe.CBg_9ambtHAnFuuj9XPrabGpi.bOhAvKAUVy X-Yahoo-Newman-Property: ymail-3 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 2F915637F; Sun, 12 Jul 2009 02:06:13 -0500 (CDT) X-Virus-Scanned: amavisd-new at noacks.org Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id XHhGCtQb27wa; Sun, 12 Jul 2009 02:06:10 -0500 (CDT) Received: from www.noacks.org (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 42ACD62BC; Sun, 12 Jul 2009 02:06:10 -0500 (CDT) Received: from 192.168.1.148 (SquirrelMail authenticated user noackjr) by www.noacks.org with HTTP; Sun, 12 Jul 2009 02:06:10 -0500 Message-ID: In-Reply-To: References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> Date: Sun, 12 Jul 2009 02:06:10 -0500 From: "Jonathan Noack" To: "Doug Rabson" , "Peter Jeremy" , freebsd-fs@freebsd.org User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Subject: Re: Booting from ZFS raidz X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2009 07:06:15 -0000 On Sun, June 14, 2009 00:09, Jonathan Noack wrote: > On Fri, May 15, 2009 19:07, Jonathan Noack wrote: >> On Thu, May 14, 2009 10:25, Doug Rabson wrote: >>> I fixed a bug in the patch. Try this version: >>> http://people.freebsd.org/~dfr/raidzboot-14052009.diff >> >> I know the bug fix was for booting from degraded pools, but I can at >> least >> give you a "no regression" report. I just set up a new amd64 box and >> was >> able to boot from a raidz1 pool using your latest patch. >> >> Getting this working from scratch was tedious but not too complicated. >> I >> followed lulf's instructions >> (http://blogs.freebsdish.org/lulf/2008/12/16/setting-up-a-zfs-only-system/) >> using the May snapshot fixit CD. Only differences were that I set up >> all >> 4 disks with gpart (identically), created a raidz1 pool, and used a >> patched gptzfsboot that I cross-compiled on my 7.2 i386 box for the >> bootcode (applied to all 4 disks). >> >> If only I had remembered to patch my /usr/src tree before rebuilding >> world >> and rebooting... *sigh* Once more unto the fixit breach... :) > > This (and the committed version) had been working fine for me on my stock > amd64 CURRENT system until I rebuilt world/kernel on 5/30 and rebooted. I > get the following error on boot (hand transcribed so hopefully I didn't > screw it up): > ************************************************************ > ZFS: i/o error - all block copies unavailable > ZFS: can't read object set for dataset lld > Can't find root filesystem - giving up > ZFS: unexpected object set type lld > ZFS: unexpected object set type lld > > FreeBSD/i386 boot > Default: tank:/boot/kernel/kernerl > boot: > ZFS: unexpected object set type lld > > FreeBSD/i386 boot > Default: tank:/boot/kernel/kernel > boot: > ************************************************************ > > The previously working world/kernel was from 5/26. I haven't had much > time to troubleshoot until today. I can use the fixit CD to access the > ZFS pool with no issues; the problem appears to just be the boot code. I > cross-built a fresh world on my i386 system today, reinstalled everything > in /boot, reinstalled gptzfsboot, and still got the same results. > > What steps should I take to troubleshoot and resolve this? Anyone know how I should proceed? I'm really frustrated that I haven't been able to get this working. Thanks, -Jon From owner-freebsd-fs@FreeBSD.ORG Sun Jul 12 21:27:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D3F7106564A; Sun, 12 Jul 2009 21:27:04 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id 0A0B68FC12; Sun, 12 Jul 2009 21:27:03 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by an-out-0708.google.com with SMTP id d14so1004633and.13 for ; Sun, 12 Jul 2009 14:27:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=BWjkRjWY3qR9CqTgtdbH21g81bh2firiJN8CsVNcOkM=; b=C3mu+p3UwgPFJtYKzzj6vrszquy2Q7EmFjD56A/8H2WVeSQnRt+NrVAYDCpkgMLBts hVZQ2b53ZWVJTOPTUzEb5WZhj9MlgVTyA9wTYMgGddps5tE0MxJDzwQsXjw6Bpp2Mn38 C6qjMj2zXfmUcaDlhgGIhN64p+wS8C44C63LM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=jWLNXIoX4jhSBbY4sJm58oO7N2BSGBhEC7H+K0tIHjRovJIARfANWaE5xJqT934zeQ +4jpV99OMiH7m/wSJsnhVqbco+YijyLLN34g/8cSSmt3ORHybvZ/jKdQgZxoPun94Tkv 0wWGqALIHZ0NzzWyg7Zx3E0dDHklcsKMLzfQc= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.32.13 with SMTP id f13mr6177594anf.36.1247434023567; Sun, 12 Jul 2009 14:27:03 -0700 (PDT) In-Reply-To: References: <72163521-40BF-4764-8B74-5446A88DFBF8@exscape.org> <45291598-D091-4E90-B968-22E59BEB3846@exscape.org> <3c1674c90907101227ueab78eem6f8c5c7fdf0337cc@mail.gmail.com> Date: Sun, 12 Jul 2009 14:27:03 -0700 X-Google-Sender-Auth: 771b2c8fc6df4e57 Message-ID: <3c1674c90907121427u5206d398pfcde8bb1cfb15f93@mail.gmail.com> From: Kip Macy To: Thomas Backman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, FreeBSD current Subject: Re: Reproducible ZFS panic, w/ script (Was: "New" ZFS crash on FS (pool?) unmount/export) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2009 21:27:04 -0000 This is caused by the timeout thread trying to execute a freed callout. It is likely just another instance of poor cleanup. -Kip > > Fatal trap 12: page fault while in kernel mode > cpuid =3D 0; apic id =3D 00 > fault virtual address =A0 =3D 0xc > fault code =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D supervisor read data, page not = present > instruction pointer =A0 =A0 =3D 0x20:0xffffffff803aa722 > stack pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff8000025a60 > frame pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff8000025a90 > code segment =A0 =A0 =A0 =A0 =A0 =A0=3D base 0x0, limit 0xfffff, type 0x1= b > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D DPL 0, pres 1, long 1,= def32 0, gran 1 > processor eflags =A0 =A0 =A0 =A0=3D resume, IOPL =3D 0 > current process =A0 =A0 =A0 =A0 =3D 12 (swi4: clock) > > ... > #8 =A00xffffffff805f1fcd in trap_fatal (frame=3D0xffffff80000259b0, eva= =3DVariable > "eva" is not available. > ) at /usr/src/sys/amd64/amd64/trap.c:847 > #9 =A00xffffffff805f2e22 in trap (frame=3D0xffffff80000259b0) at > /usr/src/sys/amd64/amd64/trap.c:345 > #10 0xffffffff805d87c7 in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:224 > #11 0xffffffff803aa722 in propagate_priority (td=3D0xffffff00296ce390) at > /usr/src/sys/kern/subr_turnstile.c:194 > #12 0xffffffff803ab58c in turnstile_wait (ts=3DVariable "ts" is not avail= able. > ) at /usr/src/sys/kern/subr_turnstile.c:738 > #13 0xffffffff8035a1c1 in _mtx_lock_sleep (m=3D0xffffffff808a1de0, > tid=3D18446742974234830624, opts=3DVariable "opts" is not available. > ) > =A0 =A0at /usr/src/sys/kern/kern_mutex.c:447 > #14 0xffffffff8037ea92 in softclock (arg=3DVariable "arg" is not availabl= e. > ) at /usr/src/sys/kern/kern_timeout.c:376 > #15 0xffffffff803417b0 in intr_event_execute_handlers (p=3DVariable "p" i= s not > available. > ) at /usr/src/sys/kern/kern_intr.c:1165 > #16 0xffffffff80342d1e in ithread_loop (arg=3D0xffffff000231e6a0) at > /usr/src/sys/kern/kern_intr.c:1178 > #17 0xffffffff8033ebb8 in fork_exit (callout=3D0xffffffff80342c90 > , arg=3D0xffffff000231e6a0, > =A0 =A0frame=3D0xffffff8000025c80) at /usr/src/sys/kern/kern_fork.c:842 > #18 0xffffffff805d8c9e in fork_trampoline () at > /usr/src/sys/amd64/amd64/exception.S:561 > #19 0x0000000000000000 in ?? () > #20 0x0000000000000000 in ?? () > #21 0x0000000000000001 in ?? () > #22 0x0000000000000000 in ?? () > #23 0x0000000000000000 in ?? () > #24 0x0000000000000000 in ?? () > #25 0x0000000000000000 in ?? () > > > Note that the active process is *not* zfs this time. > > Regards, > Thomas > --=20 When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke From owner-freebsd-fs@FreeBSD.ORG Mon Jul 13 11:06:54 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0781E1065673 for ; Mon, 13 Jul 2009 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E82B48FC12 for ; Mon, 13 Jul 2009 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n6DB6rbB040583 for ; Mon, 13 Jul 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n6DB6rOY040579 for freebsd-fs@FreeBSD.org; Mon, 13 Jul 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 13 Jul 2009 11:06:53 GMT Message-Id: <200907131106.n6DB6rOY040579@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2009 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136601 fs [zfs] tar: Couldn't list extended attributes: Read-onl o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/136218 fs [zfs] Exported ZFS pools can't be imported into (Open) o kern/135594 fs [zfs] Single dataset unresponsive with Samba o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135480 fs [zfs] panic: lock &arg.lock already initialized o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o bin/135314 fs [zfs] assertion failed for zdb(8) usage o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot f kern/134496 fs [zfs] [panic] ZFS pool export occasionally causes a ke o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133980 fs [panic] [ffs] panic: ffs_valloc: dup alloc o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [smbfs] [panic] panic: ffs_truncate: read-only filesys o kern/133373 fs [zfs] umass attachment causes ZFS checksum errors, dat o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/133134 fs [zfs] Missing ZFS zpool labels f kern/133020 fs [zfs] [panic] inappropriate panic caused by zfs. Pani o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132551 fs [zfs] ZFS locks up on extattr_list_link syscall o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132337 fs [zfs] [panic] kernel panic in zfs_fuid_create_cred o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes f kern/132068 fs [zfs] page fault when using ZFS over NFS on 7.1-RELEAS o kern/131995 fs [nfs] Failure to mount NFSv4 server o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/131086 fs [ext2fs] [patch] mkfs.ext2 creates rotten partition o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129148 fs [zfs] [panic] panic on concurrent writing & rollback o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127659 fs [tmpfs] tmpfs memory leak o kern/127492 fs [zfs] System hang on ZFS input-output o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/125644 fs [zfs] [panic] zfs unfixable fs errors caused panic whe f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o kern/122173 fs [zfs] [panic] Kernel Panic if attempting to replace a o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o kern/122047 fs [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / o kern/122038 fs [tmpfs] [panic] tmpfs: panic: tmpfs_alloc_vp: type 0xc o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o kern/121770 fs [zfs] ZFS on i386, large file or heavy I/O leads to ke o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o bin/120288 fs zfs(8): "zfs share -a" does not send SIGHUP to mountd f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B o kern/118912 fs [2tb] disk sizing/geometry problem with large array o misc/118855 fs [zfs] ZFS-related commands are nonfunctional in fixit o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118320 fs [zfs] [patch] NFS SETATTR sometimes fails to set file o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o kern/116913 fs [ffs] [panic] ffs_blkfree: freeing free block p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/115645 fs [snapshots] [panic] lockmgr: thread 0xc4c00d80, not ex o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o kern/113180 fs [zfs] Setting ZFS nfsshare property does not cause inh o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/105093 fs [ext2fs] [patch] ext2fs on read-only media cannot be m o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [iso9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna f kern/91568 fs [ufs] [panic] writing to UFS/softupdates DVD media in o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/89991 fs [ufs] softupdates with mount -ur causes fs UNREFS o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/77826 fs [ext2fs] ext2fs usb filesystem will not mount RW o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 145 problems total. From owner-freebsd-fs@FreeBSD.ORG Tue Jul 14 18:25:25 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50809106566B for ; Tue, 14 Jul 2009 18:25:25 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.freebsd.org (Postfix) with ESMTP id 1116F8FC1F for ; Tue, 14 Jul 2009 18:25:24 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by gw02.mail.saunalahti.fi (Postfix) with SMTP id DF8C21396CD for ; Tue, 14 Jul 2009 21:25:22 +0300 (EEST) Date: Tue, 14 Jul 2009 21:25:22 +0300 From: Jaakko Heinonen To: freebsd-fs@FreeBSD.org Message-ID: <20090714182522.GA40040@a91-153-125-115.elisa-laajakaista.fi> References: <20090527150258.GA3666@a91-153-125-115.elisa-laajakaista.fi> <20090619094316.GA805@a91-153-125-115.elisa-laajakaista.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090619094316.GA805@a91-153-125-115.elisa-laajakaista.fi> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: Re: VOP_WRITE & read-only file system X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2009 18:25:25 -0000 On 2009-06-19, Jaakko Heinonen wrote: > > I found a few ways to get VOP_WRITE called for a read-only system. > > > > 2) ktrace(2) - start ktracing a process - remount file-system as > > read-only > > ktrace too has a problem with writecount. ktrace uses vn_open() to > open the trace file but immediately after that it calls vn_close() > which decreases the writecount. I wrote a couple of patches for ktrace(2). > - Fiddle with writecount. IMHO it wouldn't fix the real bug (write > after vn_close()). http://www.saunalahti.fi/~jh3/patches/ktrace-writecount.diff The patch just increases v_writecount for trace file vnodes. It's quite straightforward and fixes the problem at hand but writes will still happen after vn_close()/VOP_CLOSE(). > - Keep track of vnodes which are used for tracing and have reference > count for them. http://www.saunalahti.fi/~jh3/patches/ktrace-vn_close.diff The patch uses a list to keep track of trace files. A file is closed when reference count hits zero. I am slightly concerned about scalability of the list approach but otherwise this should be more complete fix. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Wed Jul 15 00:40:03 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C25E10656E5 for ; Wed, 15 Jul 2009 00:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 06A8B8FC13 for ; Wed, 15 Jul 2009 00:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n6F0e2PR035941 for ; Wed, 15 Jul 2009 00:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n6F0e291035940; Wed, 15 Jul 2009 00:40:02 GMT (envelope-from gnats) Date: Wed, 15 Jul 2009 00:40:02 GMT Message-Id: <200907150040.n6F0e291035940@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Timothy Cleaver Cc: Subject: Re: kern/132145: [panic] File System Hard Crashes X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Timothy Cleaver List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2009 00:40:03 -0000 The following reply was made to PR kern/132145; it has been noted by GNATS. From: Timothy Cleaver To: bug-followup@FreeBSD.org, timcleaver@hotmail.com Cc: Subject: Re: kern/132145: [panic] File System Hard Crashes Date: Wed, 15 Jul 2009 10:10:57 +1000 Just to let you know, this is an ongoing problem for me. Although I haven't had a request for more information, I will supply some in the hope it sparks some interest. I am at a loss as to how to fix it. It has persisted with the move to 7.2-STABLE. Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ad0s1f 177G 56G 107G 35% 771547 23251491 3% /usr ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 390716802 (190779 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 133369856B (127 MB) Blocksize: 512 Dumptime: Tue May 26 20:41:37 2009 Hostname: pc078650.workstation.griffith.edu.au Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.2-RELEASE #0: Fri May 22 14:09:08 EST 2009 root@pc078650.workstation.griffith.edu.au:/usr/obj/usr/src/sys/KERNCONF Panic String: ffs_blkfree: freeing free block Dump Parity: 668566608 Bounds: 0 Dump Status: good Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 140001280B (133 MB) Blocksize: 512 Dumptime: Sun Jul 12 18:41:30 2009 Hostname: pc078650.workstation.griffith.edu.au Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.2-RELEASE #1: Wed Jun 3 11:36:04 EST 2009 root@pc078650.workstation.griffith.edu.au:/usr/obj/usr/src/sys/KERNCONF Panic String: ffs_valloc: dup alloc Dump Parity: 2816038494 Bounds: 1 Dump Status: good GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Unread portion of the kernel message buffer: mode = 040755, inum = 6101401, fs = /usr panic: ffs_valloc: dup alloc cpuid = 0 Uptime: 1d4h34m8s Physical memory: 494 MB Dumping 133 MB: 118 102 86 70 54 38 22 6 Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/snd_ich.ko...Reading symbols from /boot/kernel/snd_ich.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_ich.ko Reading symbols from /boot/kernel/i915.ko...Reading symbols from /boot/kernel/i915.ko.symbols...done. done. Loaded symbols for /boot/kernel/i915.ko Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done. done. Loaded symbols for /boot/kernel/drm.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/linprocfs.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/logo_saver.ko...Reading symbols from /boot/kernel/logo_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/logo_saver.ko #0 doadump () at pcpu.h:196 196 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc057832c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc05785d9 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc0747b02 in ffs_valloc (pvp=0xc40df228, mode=33188, cred=0xc4888500, vpp=0xd66f5914) at /usr/src/sys/ufs/ffs/ffs_alloc.c:987 #4 0xc07769c5 in ufs_makeinode (mode=33188, dvp=0xc40df228, vpp=0xd66f5b90, cnp=0xd66f5ba4) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2252 #5 0xc07770e0 in ufs_create (ap=0xd66f5a88) at /usr/src/sys/ufs/ufs/ufs_vnops.c:193 #6 0xc07f0ef2 in VOP_CREATE_APV (vop=0xc0872420, a=0xd66f5a88) at vnode_if.c:206 #7 0xc0606210 in vn_open_cred (ndp=0xd66f5b7c, flagp=0xd66f5c78, cmode=) at vnode_if.h:112 #8 0xc06065e3 in vn_open (ndp=0xd66f5b7c, flagp=0xd66f5c78, cmode=420, fp=0xc357c0e4) at /usr/src/sys/kern/vfs_vnops.c:94 #9 0xc0603d13 in kern_open (td=0xc35bf8c0, path=0x811fbf0
, pathseg=UIO_USERSPACE, flags=1538, mode=438) at /usr/src/sys/kern/vfs_syscalls.c:1042 #10 0xc0604280 in open (td=0xc35bf8c0, uap=0xd66f5cfc) at /usr/src/sys/kern/vfs_syscalls.c:1009 #11 0xc07daff5 in syscall (frame=0xd66f5d38) at /usr/src/sys/i386/i386/trap.c:1090 #12 0xc07bfdc0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:255 #13 0x00000033 in ?? () (kgdb) q Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 149962752B (143 MB) Blocksize: 512 Dumptime: Tue Jul 14 20:40:28 2009 Hostname: pc078650.workstation.griffith.edu.au Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.2-RELEASE #1: Wed Jun 3 11:36:04 EST 2009 root@pc078650.workstation.griffith.edu.au:/usr/obj/usr/src/sys/KERNCONF Panic String: ffs_valloc: dup alloc Dump Parity: 2165898078 Bounds: 2 Dump Status: good GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Unread portion of the kernel message buffer: mode = 0100644, inum = 2639003, fs = /usr panic: ffs_valloc: dup alloc cpuid = 0 Uptime: 2d1h44m31s Physical memory: 494 MB Dumping 143 MB: 128 112 96 80 64 48 32 16 Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/snd_ich.ko...Reading symbols from /boot/kernel/snd_ich.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_ich.ko Reading symbols from /boot/kernel/i915.ko...Reading symbols from /boot/kernel/i915.ko.symbols...done. done. Loaded symbols for /boot/kernel/i915.ko Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done. done. Loaded symbols for /boot/kernel/drm.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/linprocfs.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/logo_saver.ko...Reading symbols from /boot/kernel/logo_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/logo_saver.ko #0 doadump () at pcpu.h:196 196 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc057832c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc05785d9 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc0747b02 in ffs_valloc (pvp=0xc4fa033c, mode=33261, cred=0xc33a5900, vpp=0xd673d914) at /usr/src/sys/ufs/ffs/ffs_alloc.c:987 #4 0xc07769c5 in ufs_makeinode (mode=33261, dvp=0xc4fa033c, vpp=0xd673db90, cnp=0xd673dba4) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2252 #5 0xc07770e0 in ufs_create (ap=0xd673da88) at /usr/src/sys/ufs/ufs/ufs_vnops.c:193 #6 0xc07f0ef2 in VOP_CREATE_APV (vop=0xc0872420, a=0xd673da88) at vnode_if.c:206 #7 0xc0606210 in vn_open_cred (ndp=0xd673db7c, flagp=0xd673dc78, cmode=) at vnode_if.h:112 #8 0xc06065e3 in vn_open (ndp=0xd673db7c, flagp=0xd673dc78, cmode=493, fp=0xc351fe40) at /usr/src/sys/kern/vfs_vnops.c:94 #9 0xc0603d13 in kern_open (td=0xc5252af0, path=0x33e0f0c0
, pathseg=UIO_USERSPACE, flags=2562, mode=493) at /usr/src/sys/kern/vfs_syscalls.c:1042 #10 0xc0604280 in open (td=0xc5252af0, uap=0xd673dcfc) at /usr/src/sys/kern/vfs_syscalls.c:1009 #11 0xc07daff5 in syscall (frame=0xd673dd38) at /usr/src/sys/i386/i386/trap.c:1090 #12 0xc07bfdc0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:255 #13 0x00000033 in ?? () (kgdb) q If there is any additional information I can supply to aid in the resolution of this issue, don't hesitate to ask. From owner-freebsd-fs@FreeBSD.ORG Thu Jul 16 12:26:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79DFF1065670 for ; Thu, 16 Jul 2009 12:26:04 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id EE17A8FC23 for ; Thu, 16 Jul 2009 12:26:03 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n6GC6Kn7077092 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 16 Jul 2009 14:06:21 +0200 (CEST) (envelope-from stb@lassitu.de) (authenticated as stb) From: Stefan Bethke To: noackjr@alumni.rice.edu In-Reply-To: X-Priority: 3 (Normal) References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> Message-Id: <67089745-3E3B-45CF-B4E8-91F3B52C8A4C@lassitu.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 16 Jul 2009 14:06:19 +0200 X-Mailer: Apple Mail (2.935.3) Cc: freebsd-fs@freebsd.org Subject: Re: Booting from ZFS raidz X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 12:26:04 -0000 Am 12.07.2009 um 09:06 schrieb Jonathan Noack: > Anyone know how I should proceed? I'm really frustrated that I > haven't > been able to get this working. Me too. I just decided to revisit this, and unfortunatly, I'm still stuck with the loader having trouble reading blocks off the raidz1 volume. I've updated the creation script (see below). This is on r195709, with LOADER_ZFS_SUPPORT?=YES in /etc/make.conf. Boot output, transcribed by hand: error 4 lba 4290782259 error 4 lba 4290782258 error 4 lba 4290782259 error 4 lba 4290782258 error 4 lba 4290782257 error 4 lba 4290782257 ... error 4 lba 4292652987 error 4 lba 4292652986 error 4 lba 4292652987 BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS 638kB/2095040kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (root@freebsd-current-lassitu.de, Wed Jul 15 19:31.22 CEST 2009) Loading /boot/defaults/loader.conf ZFS: i/o error - all block copies unavailable ZFS: i/o error - all block copies unavailable ... (about 10 more of these) Unable to load a kernel! can't load 'kernel' Then the prompt. My setup script: # cat prepare-zfs-boot #!/bin/sh idx=0 label() { dd if=/dev/zero of=/dev/$1 bs=1m count=10 sz="$(diskinfo /dev/$1 | awk '{print $4}')" echo $sz gpart destroy $1 gpart create -s gpt $1 gpart add -b 34 -s 128 -t freebsd-boot -l "boot${idx}" $1 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 $1 gpart add -b 512 -s $(($sz-1024)) -t freebsd-zfs -l "zfs${idx}" $1 gpart list $1 idx="$((idx+1))" } set -x zpool destroy zroot label da1 label da2 label da3 zpool create zroot raidz /dev/gpt/zfs[0-2] zpool set bootfs=zroot zroot zfs create -V 1gb zroot/swap zfs set org.freebsd:swap=on zroot/swap zfs set checksum=off zpool/swap cd /usr/src && make installworld installkernel distribution DESTDIR=/ zroot cp /boot/loader.conf /zroot/boot/loader.conf echo 'zfs_load="YES"' >>/zroot/boot/loader.conf echo 'vfs.root.mountfrom="zfs:zroot"' >>/zroot/boot/loader.conf zpool export zroot zpool import zroot cp /boot/zfs/zpool.cache /zroot/boot/zfs/ zfs set mountpoint=legacy zroot # eof -- Stefan Bethke Fon +49 151 14070811 From owner-freebsd-fs@FreeBSD.ORG Thu Jul 16 12:28:39 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67BC81065677 for ; Thu, 16 Jul 2009 12:28:39 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id DC25C8FC1D for ; Thu, 16 Jul 2009 12:28:38 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n6GCSbIb077735 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 16 Jul 2009 14:28:38 +0200 (CEST) (envelope-from stb@lassitu.de) (authenticated as stb) Message-Id: <3F75A414-1D5F-4692-B3B1-41EBCC1A22D2@lassitu.de> From: Stefan Bethke To: freebsd-fs@freebsd.org In-Reply-To: <67089745-3E3B-45CF-B4E8-91F3B52C8A4C@lassitu.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) X-Priority: 3 (Normal) Date: Thu, 16 Jul 2009 14:28:37 +0200 References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> <67089745-3E3B-45CF-B4E8-91F3B52C8A4C@lassitu.de> X-Mailer: Apple Mail (2.935.3) Subject: Re: Booting from ZFS raidz X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 12:28:39 -0000 Am 16.07.2009 um 14:06 schrieb Stefan Bethke: > Am 12.07.2009 um 09:06 schrieb Jonathan Noack: > >> Anyone know how I should proceed? I'm really frustrated that I >> haven't >> been able to get this working. > > Me too. I just decided to revisit this, and unfortunatly, I'm still > stuck with the loader having trouble reading blocks off the raidz1 > volume. I've updated the creation script (see below). This is on > r195709, with LOADER_ZFS_SUPPORT?=YES in /etc/make.conf. I just checked that my basic procedure is sane by creating a single vdev pool (zpool create /dev/gpt/zfs0), and that is booting and working just fine. Stefan -- Stefan Bethke Fon +49 151 14070811 From owner-freebsd-fs@FreeBSD.ORG Fri Jul 17 15:24:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAE201065672 for ; Fri, 17 Jul 2009 15:24:49 +0000 (UTC) (envelope-from arnaud.houdelette@tzim.net) Received: from golanth.tzim.net (unknown [IPv6:2001:41d0:1:d91f:21c:c0ff:fe4b:cf32]) by mx1.freebsd.org (Postfix) with ESMTP id 641728FC0C for ; Fri, 17 Jul 2009 15:24:49 +0000 (UTC) (envelope-from arnaud.houdelette@tzim.net) Received: from alarante.irisa.fr ([131.254.13.244]) by golanth.tzim.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MRpIm-000Mhz-8p; Fri, 17 Jul 2009 17:24:48 +0200 Message-ID: <4A6097BA.8030305@tzim.net> Date: Fri, 17 Jul 2009 17:24:42 +0200 From: Arnaud Houdelette User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Stefan Bethke References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> <67089745-3E3B-45CF-B4E8-91F3B52C8A4C@lassitu.de> <3F75A414-1D5F-4692-B3B1-41EBCC1A22D2@lassitu.de> In-Reply-To: <3F75A414-1D5F-4692-B3B1-41EBCC1A22D2@lassitu.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-User: tzim@tzim.net X-Authenticator: plain Cc: freebsd-fs@freebsd.org Subject: Re: Booting from ZFS raidz X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2009 15:24:50 -0000 Stefan Bethke a écrit : > Am 16.07.2009 um 14:06 schrieb Stefan Bethke: > >> Am 12.07.2009 um 09:06 schrieb Jonathan Noack: >> >>> Anyone know how I should proceed? I'm really frustrated that I haven't >>> been able to get this working. >> >> Me too. I just decided to revisit this, and unfortunatly, I'm still >> stuck with the loader having trouble reading blocks off the raidz1 >> volume. I've updated the creation script (see below). This is on >> r195709, with LOADER_ZFS_SUPPORT?=YES in /etc/make.conf. > > I just checked that my basic procedure is sane by creating a single > vdev pool (zpool create /dev/gpt/zfs0), and that is booting and > working just fine. > > > Stefan > I got the same kind of errors with 8.0-BETA1 (rebuilt loader with ZFS_SUPPORT) with raidz on a VirtualBox. I however got some hints : Tried with single disk on pool : works like a charm. Tried with a mirror : the loader only 'sees' the first disk. Could that be the source of our problems ? BTX loader only shows drives A: and C: lsdev -v gives : cd devices: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: disk1p1: FreeBSD boot 64KB disk1p2: FreeBSD ZFS 19GB pxe devices: zfs devices: pool: zroot config: NAME STATE zroot DEGRADED mirror DEGRADED gpt/zfs1 ONLINE gpt/zfs2 OFFLINE As the mirror is degraded but readable, the loader is able to boot. Could it be a BIOS or boot0 problem ? Arnaud From owner-freebsd-fs@FreeBSD.ORG Fri Jul 17 15:50:30 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2D4A1065680 for ; Fri, 17 Jul 2009 15:50:30 +0000 (UTC) (envelope-from seyes463@gmail.com) Received: from mail-ew0-f220.google.com (mail-ew0-f220.google.com [209.85.219.220]) by mx1.freebsd.org (Postfix) with ESMTP id 549848FC1C for ; Fri, 17 Jul 2009 15:50:29 +0000 (UTC) (envelope-from seyes463@gmail.com) Received: by ewy20 with SMTP id 20so756591ewy.43 for ; Fri, 17 Jul 2009 08:50:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Xs6V4f35lYSdm3slbJmArTlRhBx9nVCYEMZVoNnFAFc=; b=Nczv8h3VuwnMSEgrbIROL819ILOfpoSr9X4sULAPcKQGLQkKX2v5gTpeMKk0HC+GfJ rL++Z78SpWS5m5CU9ENZSIKWD5HQ/j8ONgNzHiycCrG/iVIvuK9qnswbWEkx+gnhaczt sE49EQ8qL0xoz9Bhpiw71jSns+Igd3CHBcAw0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=NqkIKg8QNlPwB/DGoKotZoIqdRrxGNYyXMYvz84aVilTbv1d5VI7TUFFqDM4hWxPft xeAIyf0IF7wrRgE68VyS0ZDThVjSWejsFg1Q/OdN8PvwO5X84MQWjGltDAcUu9I4wC7r o2sJH7sr1AAfz0IMIpG+Ws8Whj9Xyen9AB1S8= MIME-Version: 1.0 Received: by 10.216.28.85 with SMTP id f63mr329075wea.142.1247843997091; Fri, 17 Jul 2009 08:19:57 -0700 (PDT) Date: Fri, 17 Jul 2009 09:19:57 -0600 Message-ID: <1d8e056d0907170819k368dbb4s34445441fd56d74d@mail.gmail.com> From: Snakey Eyes To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: kern/118107: [ntfs] [panic] Kernel panic when accessing a file at NTFS file system [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2009 15:50:31 -0000 I'm running into this bug and would like to help out with testing/resolving. Is this the appropriate place to start? From owner-freebsd-fs@FreeBSD.ORG Fri Jul 17 16:22:16 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1366E106566B for ; Fri, 17 Jul 2009 16:22:16 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 9D9CB8FC1A for ; Fri, 17 Jul 2009 16:22:15 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n6HGMDUg055108 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jul 2009 18:22:14 +0200 (CEST) (envelope-from stb@lassitu.de) (authenticated as stb) Message-Id: From: Stefan Bethke To: Arnaud Houdelette In-Reply-To: <4A6097BA.8030305@tzim.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v935.3) Date: Fri, 17 Jul 2009 18:22:13 +0200 References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> <67089745-3E3B-45CF-B4E8-91F3B52C8A4C@lassitu.de> <3F75A414-1D5F-4692-B3B1-41EBCC1A22D2@lassitu.de> <4A6097BA.8030305@tzim.net> X-Mailer: Apple Mail (2.935.3) Cc: freebsd-fs@freebsd.org Subject: Re: Booting from ZFS raidz X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2009 16:22:16 -0000 Am 17.07.2009 um 17:24 schrieb Arnaud Houdelette: > Stefan Bethke a =E9crit : >> Am 16.07.2009 um 14:06 schrieb Stefan Bethke: >> >>> Am 12.07.2009 um 09:06 schrieb Jonathan Noack: >>> >>>> Anyone know how I should proceed? I'm really frustrated that I =20 >>>> haven't >>>> been able to get this working. >>> >>> Me too. I just decided to revisit this, and unfortunatly, I'm =20 >>> still stuck with the loader having trouble reading blocks off the =20= >>> raidz1 volume. I've updated the creation script (see below). =20 >>> This is on r195709, with LOADER_ZFS_SUPPORT?=3DYES in = /etc/make.conf. >> >> I just checked that my basic procedure is sane by creating a single =20= >> vdev pool (zpool create /dev/gpt/zfs0), and that is booting and =20 >> working just fine. >> >> >> Stefan >> > I got the same kind of errors with 8.0-BETA1 (rebuilt loader with =20 > ZFS_SUPPORT) with raidz on a VirtualBox. > I however got some hints : > Tried with single disk on pool : works like a charm. > Tried with a mirror : the loader only 'sees' the first disk. Could =20 > that be the source of our problems ? > > BTX loader only shows drives A: and C: > > lsdev -v gives : > cd devices: > disk devices: > disk0: BIOS drive A: > disk1: BIOS drive C: > disk1p1: FreeBSD boot 64KB > disk1p2: FreeBSD ZFS 19GB > pxe devices: > zfs devices: > pool: zroot > config: > > NAME STATE > zroot DEGRADED > mirror DEGRADED > gpt/zfs1 ONLINE > gpt/zfs2 OFFLINE > > As the mirror is degraded but readable, the loader is able to boot. > Could it be a BIOS or boot0 problem ? In VMware Fusion, it appears the loader sees all disks (with my UFS =20 disk attached, and with ZFS on raw devices: OK lsdev -v cd devices: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: disk1s1a: FFS 30GB (2097215 - 67103505) disk1s1b: swap 1024MB (63 - 2097215) disk2: BIOS drive D: disk2: FFS bad disklabel disk3: BIOS drive E: disk3: FFS bad disklabel disk4: BIOS drive F: disk4: FFS bad disklabel pxe devices: zfs devices: pool: zroot config: NAME STATE zroot ONLINE raidz1 ONLINE da1 ONLINE da2 ONLINE da3 ONLINE OK When detaching the first disk, so that only the three ZFS disks are =20 available, I get the same output (but loader error on trying to read =20 the kernel, as posted previously). Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-fs@FreeBSD.ORG Fri Jul 17 16:31:05 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE004106566B for ; Fri, 17 Jul 2009 16:31:05 +0000 (UTC) (envelope-from jgfredo@gmail.com) Received: from mail-pz0-f193.google.com (mail-pz0-f193.google.com [209.85.222.193]) by mx1.freebsd.org (Postfix) with ESMTP id 80A9D8FC16 for ; Fri, 17 Jul 2009 16:31:05 +0000 (UTC) (envelope-from jgfredo@gmail.com) Received: by pzk31 with SMTP id 31so646166pzk.3 for ; Fri, 17 Jul 2009 09:31:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:x-mailer:mime-version :subject:date; bh=ZansUW/KcfZiIT/Z5qA59pcnfBZqG5fMq2kBd7/ch7o=; b=lCPUv3jfUpTPNgfIgJ8MXACOyDXC2x4Q2S6zRK5Ar4WVX79t581P4r/h8VuzbEP32p pEt6Q/WlROCMzDzBS755t8gSILab0Z9zKPnNvUhFzQGhofzpyfHZ7BRHBhCGCJwePrcn ZGrfIg5dQqOB33gtK0LxWKYnHCJgjagTvyMlg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date; b=Ai1inVy6jqzclkZbwrmT3FIzfeZPDnE06jUCuol3A3jdTEHW8tGH+TVempfYoO4Rbf SbC14aD+gZw1Gs3b6SE8le4U0AcjgOyb1lHb1AxatF+pwEcTSzFVHrjLkGi6m4kAynXx XXoN6L06QhhLX5pTSXXvXGzXp2hViu2OAKgJg= Received: by 10.142.155.13 with SMTP id c13mr260575wfe.145.1247846525660; Fri, 17 Jul 2009 09:02:05 -0700 (PDT) Received: from ?126.247.15.83? (pw126247015083.7.tik.panda-world.ne.jp [126.247.15.83]) by mx.google.com with ESMTPS id 30sm4114372wfd.23.2009.07.17.09.02.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 17 Jul 2009 09:02:04 -0700 (PDT) Message-Id: <0584EF0B-B93A-4765-9510-0EA06B9D4BAE@gmail.com> From: "Fred J.G." To: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A341) Mime-Version: 1.0 (iPhone Mail 7A341) Date: Sat, 18 Jul 2009 01:01:33 +0900 Subject: Re: FreeBSD, SSD's and partition alignment X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2009 16:31:05 -0000 Dear All, In reference to this issue about SSD's and partition alignment at http://kerneltrap.org/mailarchive/freebsd-fs/2009/1/5/4601614 I have been struggling a few hours with installing FreeBSD on a SSD attached to a VIA-EPIA Mini ITX board with the VIA PLE133 Chipset on it. I have choosen FreeBSD specifically because it appeared already running as os with samba on this commercial NAS-device based on the VIA EPIA board with many interesting neglected features. The 5400rpm internal drive is retired from today. After getting a lot of inode errors when trying to install FreeBSD 7.2 on a OCZ PATA 120GB SSD attached to IDE1 interface of the board I ended up to follow up the Geometry reported by the BIOS C/H/S = 61865/16/255 . Surprisingly or maybe not surprisingly to readers here no inode errors anymore during a full installation! I do have some concerns though regarding wearing and performance ( degradation)such as: - The default newfs args -b 16384 -f 2048 will this be in harmony? - Currently 1GB memory onboard and default 2GB swap is defined on the SSD. - etc. out of my current perception... Further it is a great learning project since this board is more than 6 years old but reasonable in power consumption. the ultimate goal is to create a thinfat client annex voip videophone multimedia box which will be able to connect to a virtualized featherweight virtual machine somewhere. if kerneloptimalisation is required for this than it be so. looking forward to any constructive input. cheers, Fred