From owner-freebsd-fs@FreeBSD.ORG Sun Feb 15 10:40:00 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 6235A1065670; Sun, 15 Feb 2009 10:40:00 +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 E420C8FC14; Sun, 15 Feb 2009 10:39:59 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n1FAe22M002211 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 15 Feb 2009 11:40:03 +0100 (CET) (envelope-from stb@lassitu.de) (authenticated as stb) Message-Id: <3A302EE1-F54D-4415-BC13-CA8ABBA320EC@lassitu.de> From: Stefan Bethke To: freebsd-fs@freebsd.org In-Reply-To: <76873DDF-D21B-48AF-9AFB-5A2747BE406B@lassitu.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 15 Feb 2009 11:39:57 +0100 References: <76873DDF-D21B-48AF-9AFB-5A2747BE406B@lassitu.de> X-Mailer: Apple Mail (2.930.3) Cc: Pawel Jakub Dawidek Subject: Re: zfs: using, then destroying a snapshot sometimes panics zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2009 10:40:00 -0000 Am 08.02.2009 um 14:37 schrieb Stefan Bethke: > Sorry I can't be more precise at the moment, but while creating a > script that mirrors some zfs filesystems to another machine, I've > now twice gotten weird behaviour and then a panic. > > The script iterates over a couple of zfs file systems: > - creates a snapshot with zfs snapshot tank/foo@mirror > - uses rsync to copy the contents of the snapshot with rsync /tank/ > foo/.zfs/snapshot/mirror/ dest:... > - destroys the snapshot with zfs destroy tank/foo@mirror > > During testing the script, I twice got to a point where, after the > snapshot was created without an error message, rsync dropped out > with an error message similar to "invalid file handle" on /tank/ > foo/.zfs/snapshot. > > At that point, I could cd to /tank/foo/.zfs, but ls produced the > same error message. > > I then tried to unmount the snapshot with zfs umount, and got a > panic (which I also didn't manage to capture). > > Is this a generally known issue, or should I try to capture more > information when this happens again? # cd /tank/foo/.zfs # ls -l ls: snapshot: Bad file descriptor total 0 # cd snapshot -su: cd: snapshot: Not a directory I currently have no snapshots: # zfs list -t snapshot no datasets available However, on a different file system, I can list and cd into snapshot: # /tank/bar/.zfs # ls -l total 0 dr-xr-xr-x 2 root wheel 2 Feb 8 00:43 snapshot/ # cd snapshot Trying to umount produces a panic: # zfs umount /jail/foo Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xa8 fault code = supervisor write data, page not present instruction pointer = 0x8:0xffffffff802ee565 stack pointer = 0x10:0xfffffffea29c39e0 frame pointer = 0x10:0xfffffffea29c39f0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 51383 (zfs) [thread pid 51383 tid 100298 ] Stopped at _sx_xlock+0x15: lock cmpxchgq %rsi,0x18(%rdi) db> bt Tracing pid 51383 tid 100298 td 0xffffff00a598e720 _sx_xlock() at _sx_xlock+0x15 zfsctl_umount_snapshots() at zfsctl_umount_snapshots+0xa5 zfs_umount() at zfs_umount+0xdd dounmount() at dounmount+0x2b4 unmount() at unmount+0x24b syscall() at syscall+0x1a5 Xfast_syscall() at Xfast_syscall+0xab --- syscall (22, FreeBSD ELF64, unmount), rip = 0x800f412fc, rsp = 0x7fffffffd1a8, rbp = 0x801202300 --- db> call doadump Physical memory: 3314 MB Dumping 1272 MB: 1257 1241 1225 1209 1193 1177 1161 1145 1129 1113 1097 1081 1065 1049 1033 1017 1001 985 969 953 937 921 905 889 873 857 841 825 809 793 777 761 745 729 713 697 681 665 649 633 617 601 585 569 553 537 521 505 489 473 457 441 425 409 393 377 361 345 329 313 297 281 265 249 233 217 201 185 169 153 137 121 105 89 73 57 41 25 9 Dump complete = 0 I've got the crashdump saved, if there's any information in there that can be helpful. This is -current from a week ago on amd64. At the current rate, this happens every couple of days, so gathering more information on the live system probably won't be a problem. Stefan -- Stefan Bethke Fon +49 151 14070811 From owner-freebsd-fs@FreeBSD.ORG Sun Feb 15 11:08:55 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D1791065670; Sun, 15 Feb 2009 11:08:55 +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 CA1D68FC1B; Sun, 15 Feb 2009 11:08:54 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n1FB8qhw003595 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 15 Feb 2009 12:08:53 +0100 (CET) (envelope-from stb@lassitu.de) (authenticated as stb) Message-Id: <171C5946-63D1-4AC7-89F7-A951BEF3D1C6@lassitu.de> From: Stefan Bethke To: freebsd-fs@freebsd.org In-Reply-To: <3A302EE1-F54D-4415-BC13-CA8ABBA320EC@lassitu.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 15 Feb 2009 12:08:52 +0100 References: <76873DDF-D21B-48AF-9AFB-5A2747BE406B@lassitu.de> <3A302EE1-F54D-4415-BC13-CA8ABBA320EC@lassitu.de> X-Mailer: Apple Mail (2.930.3) Cc: Pawel Jakub Dawidek Subject: Re: zfs: using, then destroying a snapshot sometimes panics zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2009 11:08:55 -0000 Am 15.02.2009 um 11:39 schrieb Stefan Bethke: > Am 08.02.2009 um 14:37 schrieb Stefan Bethke: > >> Sorry I can't be more precise at the moment, but while creating a >> script that mirrors some zfs filesystems to another machine, I've >> now twice gotten weird behaviour and then a panic. >> >> The script iterates over a couple of zfs file systems: >> - creates a snapshot with zfs snapshot tank/foo@mirror >> - uses rsync to copy the contents of the snapshot with rsync /tank/ >> foo/.zfs/snapshot/mirror/ dest:... >> - destroys the snapshot with zfs destroy tank/foo@mirror >> >> During testing the script, I twice got to a point where, after the >> snapshot was created without an error message, rsync dropped out >> with an error message similar to "invalid file handle" on /tank/ >> foo/.zfs/snapshot. >> >> At that point, I could cd to /tank/foo/.zfs, but ls produced the >> same error message. >> >> I then tried to unmount the snapshot with zfs umount, and got a >> panic (which I also didn't manage to capture). >> >> Is this a generally known issue, or should I try to capture more >> information when this happens again? > > > # cd /tank/foo/.zfs > # ls -l > ls: snapshot: Bad file descriptor > total 0 > # cd snapshot > -su: cd: snapshot: Not a directory > > I currently have no snapshots: > # zfs list -t snapshot > no datasets available > > However, on a different file system, I can list and cd into snapshot: > # /tank/bar/.zfs > # ls -l > total 0 > dr-xr-xr-x 2 root wheel 2 Feb 8 00:43 snapshot/ > # cd snapshot > > Trying to umount produces a panic: > # zfs umount /jail/foo > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0xa8 > fault code = supervisor write data, page not present > instruction pointer = 0x8:0xffffffff802ee565 > stack pointer = 0x10:0xfffffffea29c39e0 > frame pointer = 0x10:0xfffffffea29c39f0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 51383 (zfs) > [thread pid 51383 tid 100298 ] > Stopped at _sx_xlock+0x15: lock cmpxchgq %rsi,0x18(%rdi) > db> bt > Tracing pid 51383 tid 100298 td 0xffffff00a598e720 > _sx_xlock() at _sx_xlock+0x15 > zfsctl_umount_snapshots() at zfsctl_umount_snapshots+0xa5 > zfs_umount() at zfs_umount+0xdd > dounmount() at dounmount+0x2b4 > unmount() at unmount+0x24b > syscall() at syscall+0x1a5 > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (22, FreeBSD ELF64, unmount), rip = 0x800f412fc, rsp = > 0x7fffffffd1a8, rbp = 0x801202300 --- > db> call doadump > Physical memory: 3314 MB > Dumping 1272 MB: 1257 1241 1225 1209 1193 1177 1161 1145 1129 1113 > 1097 1081 1065 1049 1033 1017 1001 985 969 953 937 921 905 889 873 > 857 841 825 809 793 777 761 745 729 713 697 681 665 649 633 617 601 > 585 569 553 537 521 505 489 473 457 441 425 409 393 377 361 345 329 > 313 297 281 265 249 233 217 201 185 169 153 137 121 105 89 73 57 41 > 25 9 > Dump complete > = 0 > > I've got the crashdump saved, if there's any information in there > that can be helpful. > > This is -current from a week ago on amd64. > > At the current rate, this happens every couple of days, so gathering > more information on the live system probably won't be a problem. Different machine, identical configuration, I just got this panic on reboot: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xa8 fault code = supervisor write data, page not present instruction pointer = 0x8:0xffffffff802ee3b5 stack pointer = 0x10:0xfffffffe40016980 frame pointer = 0x10:0xfffffffe40016990 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1 (init) [thread pid 1 tid 100002 ] Stopped at _sx_xlock+0x15: lock cmpxchgq %rsi,0x18(%rdi) db> bt Tracing pid 1 tid 100002 td 0xffffff000141fab0 _sx_xlock() at _sx_xlock+0x15 zfsctl_umount_snapshots() at zfsctl_umount_snapshots+0xa5 zfs_umount() at zfs_umount+0xdd dounmount() at dounmount+0x2b4 vfs_unmountall() at vfs_unmountall+0x42 boot() at boot+0x655 reboot() at reboot+0x42 syscall() at syscall+0x1a5 Xfast_syscall() at Xfast_syscall+0xab --- syscall (55, FreeBSD ELF64, reboot), rip = 0x40897c, rsp = 0x7fffffffe7b8, rbp = 0x402420 --- -- Stefan Bethke Fon +49 151 14070811 From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 05:18:02 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 15FF8106566B; Mon, 16 Feb 2009 05:18:02 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.freebsd.org (Postfix) with ESMTP id D52368FC15; Mon, 16 Feb 2009 05:18:01 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from localhost (pool-141-151-14-70.phlapa.east.verizon.net [141.151.14.70]) by mail.asahi-net.or.jp (Postfix) with ESMTP id A28075D45E; Mon, 16 Feb 2009 14:00:47 +0900 (JST) Date: Mon, 16 Feb 2009 00:00:44 -0500 From: Yoshihiro Ota To: Xin LI , =?UTF-8?B?6KO05Zu95YW0?= Message-Id: <20090216000044.d77fec80.ota@j.email.ne.jp> In-Reply-To: <499531A4.3020308@delphij.net> References: <98869b7c0902100112s6dae54bm4c14487076ceb75c@mail.gmail.com> <20090212183440.GA1446@tops> <20090213001350.52470f39.ota@j.email.ne.jp> <499531A4.3020308@delphij.net> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.11; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Gleb Kurtsou , freebsd-current@freebsd.org, imura@FreeBSD.org Subject: RE: patch: let msdosfs(vfat)/ntfs to support UTF-8 locale well X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 05:18:02 -0000 FYI: This is another person who attempted the same or similar. It begins with the following one and got a couple of replies. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=262846+0+archive/2006/freebsd-hackers/20060813.freebsd-hackers Is anyone intend to work on this issue? Regards, Hiro On Fri, 13 Feb 2009 00:39:00 -0800 Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > (cc'ed to freebsd-fs@) > > I think it's important that someone familiar with the code review and > evaluate the current patches and commit it against -HEAD... > > MSDOSFS patch (against 7.1): > http://btload.googlegroups.com/web/msdosfs.patch?gda=MzIscT8AAABs_gmy4a1S9lRiXjEy-V5OpwtI67JnIGlz0zr18tjObOtoi5oIt3BJMRGeqGBbbj-ccyFKn-rNKC-d1pM_IdV0 > NTFS patch: > http://btload.googlegroups.com/web/ntfs.patch?gda=OqsHoDwAAABs_gmy4a1S9lRiXjEy-V5O7RN7t-m4MjZ-5dQn_EvaqDVCWO9_HyYEQJyRQYPtRCL9Wm-ajmzVoAFUlE7c_fAt > > Cheers, > - -- > Xin LI http://www.delphij.net/ > FreeBSD - The Power to Serve! > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.10 (FreeBSD) > > iEUEARECAAYFAkmVMaQACgkQi+vbBBjt66DN+wCghJbOUO7IfEwt5gFOB01uAAe1 > NLwAmOQXPJsB+lT7o5MMk16Ck6eUJrQ= > =ZGMA > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 11:06:50 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7683106566B for ; Mon, 16 Feb 2009 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C3A3D8FC20 for ; Mon, 16 Feb 2009 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1GB6oI9096108 for ; Mon, 16 Feb 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1GB6o2I096104 for freebsd-fs@FreeBSD.org; Mon, 16 Feb 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Feb 2009 11:06:50 GMT Message-Id: <200902161106.n1GB6o2I096104@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, 16 Feb 2009 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131353 fs gjournal kernel lock o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/131086 fs [ext2fs] mkfs.ext2 creates rotten partition o kern/131084 fs [xfs] xfs destroys itself after copying data o kern/131081 fs [zfs] User cannot delete a file when a ZFS dataset is o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o bin/130105 fs [zfs] zfs send -R dumps core o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129174 fs [nfs] [zfs] [panic] NFS v3 Panic when under high load o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129084 fs [udf] [panic] [lor] udf panic: getblk: size(67584) > M f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po 42 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 15:15:23 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 A3BE710657DB for ; Mon, 16 Feb 2009 15:15:23 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 629538FC18 for ; Mon, 16 Feb 2009 15:15:23 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 72FFD6D43F; Mon, 16 Feb 2009 15:15:22 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 5547D844DE; Mon, 16 Feb 2009 16:15:22 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Andrew Brampton References: <868wp4pqwm.fsf@ds4.des.no> <86iqo74ba1.fsf@ds4.des.no> Date: Mon, 16 Feb 2009 16:15:22 +0100 In-Reply-To: (Andrew Brampton's message of "Fri, 23 Jan 2009 14:05:55 +0000") Message-ID: <86y6w6tnud.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs Subject: Re: Pseudofs and pfs_attr_t for non-process based files X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 15:15:26 -0000 Andrew Brampton writes: > Here are both patches again, but only the procfs patch has changed. I > have now removed the redundant code. Sorry, I had completely forgotten about these. I'll commit them ASAP. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 15:17:37 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 29F5A1065781 for ; Mon, 16 Feb 2009 15:17:37 +0000 (UTC) (envelope-from brampton@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 1682E8FC21 for ; Mon, 16 Feb 2009 15:17:34 +0000 (UTC) (envelope-from brampton@gmail.com) Received: by ewy14 with SMTP id 14so2138436ewy.19 for ; Mon, 16 Feb 2009 07:17:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=YPYOZTD2dcN5sIEOpF1OH9dcIWyg6NdFL9iJsAhl5LE=; b=kOLy74A71+r3gNQCwEZxyiJKjevTiFjUAPedFlc1CDWbXNiDB6IikkBoPpsxTRpGd7 vn+hTRZo0UP/Q/FRAYI4AYvseYBU29xC4irKb2DwyXCNwsqOvb572R2uVb/RzjkKADhj EqBy8mTR7FRXcLO3wWagonq2hCRe3p6EH30tM= 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=hwkn6pAGn0epwJbnQs3/MPV4mlCrKiQHIHoWeE9OCrB3M9usPHWs7GRI7DXBYvIzrw 5EgQYPFaR+xHNvfDzAn+inZpMEqohd6ofl+DKW9WwEGvoW8+4Doalgyhflf1M4FIio7P eAED3qHgZe9MvlHqNo/evmLDsKI7PMLqJg9L8= MIME-Version: 1.0 Sender: brampton@gmail.com Received: by 10.210.117.1 with SMTP id p1mr4435953ebc.163.1234797453986; Mon, 16 Feb 2009 07:17:33 -0800 (PST) In-Reply-To: <86y6w6tnud.fsf@ds4.des.no> References: <868wp4pqwm.fsf@ds4.des.no> <86iqo74ba1.fsf@ds4.des.no> <86y6w6tnud.fsf@ds4.des.no> Date: Mon, 16 Feb 2009 15:17:33 +0000 X-Google-Sender-Auth: 70a2388c3093173b Message-ID: From: Andrew Brampton To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs Subject: Re: Pseudofs and pfs_attr_t for non-process based files X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 15:17:38 -0000 Thanks, To which branch will they be commited? 7.1 or 8.0? thanks Andrew 2009/2/16 Dag-Erling Sm=C3=B8rgrav : > Andrew Brampton writes: >> Here are both patches again, but only the procfs patch has changed. I >> have now removed the redundant code. > > Sorry, I had completely forgotten about these. I'll commit them ASAP. > > DES > -- > Dag-Erling Sm=C3=B8rgrav - des@des.no > From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 15:28: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 C9132106566C for ; Mon, 16 Feb 2009 15:28:15 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 880EA8FC12 for ; Mon, 16 Feb 2009 15:28:15 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 930A96D43F; Mon, 16 Feb 2009 15:28:14 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 76D6A844DE; Mon, 16 Feb 2009 16:28:14 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Andrew Brampton References: <868wp4pqwm.fsf@ds4.des.no> <86iqo74ba1.fsf@ds4.des.no> <86y6w6tnud.fsf@ds4.des.no> Date: Mon, 16 Feb 2009 16:28:14 +0100 In-Reply-To: (Andrew Brampton's message of "Mon, 16 Feb 2009 15:17:33 +0000") Message-ID: <86mycmtn8x.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs Subject: Re: Pseudofs and pfs_attr_t for non-process based files X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 15:28:16 -0000 Andrew Brampton writes: > To which branch will they be commited? 7.1 or 8.0? head about 10 minutes ago, stable/7 will follow in a couple of weeks. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 16:31:27 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 AB85A1065675; Mon, 16 Feb 2009 16:31:27 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 80D9C8FC13; Mon, 16 Feb 2009 16:31:27 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1GGVRRu052524; Mon, 16 Feb 2009 16:31:27 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1GGVRdn052520; Mon, 16 Feb 2009 16:31:27 GMT (envelope-from linimon) Date: Mon, 16 Feb 2009 16:31:27 GMT Message-Id: <200902161631.n1GGVRdn052520@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/131743: [ext2fs] utf-8 file names of ext2 partitions cause problems 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, 16 Feb 2009 16:31:28 -0000 Old Synopsis: utf-8 file names of ext2 partitions cause problems New Synopsis: [ext2fs] utf-8 file names of ext2 partitions cause problems Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Feb 16 16:31:11 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131743 From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 17: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 B30761065670 for ; Mon, 16 Feb 2009 17: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 A1CEF8FC0C for ; Mon, 16 Feb 2009 17: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 n1GHe3BJ001275 for ; Mon, 16 Feb 2009 17:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1GHe3Uj001274; Mon, 16 Feb 2009 17:40:03 GMT (envelope-from gnats) Date: Mon, 16 Feb 2009 17:40:03 GMT Message-Id: <200902161740.n1GHe3Uj001274@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Jaakko Heinonen Cc: Subject: Re: kern/131743: utf-8 file names of ext2 partitions cause problems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jaakko Heinonen List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 17:40:04 -0000 The following reply was made to PR kern/131743; it has been noted by GNATS. From: Jaakko Heinonen To: Elmar Stellnberger Cc: bug-followup@FreeBSD.org Subject: Re: kern/131743: utf-8 file names of ext2 partitions cause problems Date: Mon, 16 Feb 2009 19:38:33 +0200 On 2009-02-16, Elmar Stellnberger wrote: > >Class: sw-bug > FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and > utf8 options. The consequence are not only wrongly displayed file > names. I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8 encoded file names providing that you have configured locale settings correctly. Do you expect "iocharset=utf8" and "utf8" mount options to convert file names to some other encoding? AFAIK even Linux doesn't support such options for ext2. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Mon Feb 16 18:50:02 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 68FBC106566B for ; Mon, 16 Feb 2009 18:50:02 +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 55CD78FC2A for ; Mon, 16 Feb 2009 18:50:02 +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 n1GIo2L9054732 for ; Mon, 16 Feb 2009 18:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1GIo2FX054731; Mon, 16 Feb 2009 18:50:02 GMT (envelope-from gnats) Date: Mon, 16 Feb 2009 18:50:02 GMT Message-Id: <200902161850.n1GIo2FX054731@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Elmar Stellnberger Cc: Subject: Re: Re: kern/131743: utf-8 file names of ext2 partitions cause problems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Elmar Stellnberger List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 18:50:02 -0000 The following reply was made to PR kern/131743; it has been noted by GNATS. From: Elmar Stellnberger To: bug-followup@FreeBSD.org, jh@saunalahti.fi Cc: Subject: Re: Re: kern/131743: utf-8 file names of ext2 partitions cause problems Date: Mon, 16 Feb 2009 18:50:45 +0000 This is a multi-part message in MIME format. --------------070101080609050401060407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Basically I would expect the utf8 file system option to convert from utf8 to whatever charset is selected by default at the moment. I will have to have another look on how to enable utf8 on FreeBSD. Previously consulted web resources have not worked as expected. Nevertheless if enabling utf8 as default charset is all I need to do in order to view and access these files correctly that should be fine for me. thx for any further hint. On 2009-02-16, Elmar Stellnberger wrote: >> > >Class: sw-bug >> > > FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and > > utf8 options. The consequence are not only wrongly displayed file > > names. > I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8 encoded file names providing that you have configured locale settings correctly. Do you expect "iocharset=utf8" and "utf8" mount options to convert file names to some other encoding? AFAIK even Linux doesn't support such options for ext2. -- Jaakko --------------070101080609050401060407 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Basically I would expect the utf8 file system option to convert from utf8 to whatever charset is selected by default at the moment.
I will have to have another look on how to enable utf8 on FreeBSD. Previously consulted web resources have not worked as expected.
Nevertheless if enabling utf8 as default charset is all I need to do in order to view and access these files correctly that should be fine for me.
thx for any further hint.

On 2009-02-16, Elmar Stellnberger wrote:
 
> >Class:          sw-bug
     

 
> FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and
 > utf8 options. The consequence are not only wrongly displayed file
 > names.
   

 I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8
 encoded file names providing that you have configured locale settings
 correctly.
 
 Do you expect "iocharset=utf8" and "utf8" mount options to convert
 file names to some other encoding? AFAIK even Linux doesn't support such
 options for ext2.
 
 
-- 
 Jaakko

--------------070101080609050401060407-- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 18 12:20: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 82BE8106564A for ; Wed, 18 Feb 2009 12:20: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 65C0E8FC08 for ; Wed, 18 Feb 2009 12:20: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 n1ICK3kO077777 for ; Wed, 18 Feb 2009 12:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1ICK3aZ077776; Wed, 18 Feb 2009 12:20:03 GMT (envelope-from gnats) Date: Wed, 18 Feb 2009 12:20:03 GMT Message-Id: <200902181220.n1ICK3aZ077776@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Elmar Stellnberger Cc: Subject: Re: kern/131743: utf-8 file names of ext2 partitions cause problems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Elmar Stellnberger List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2009 12:20:03 -0000 The following reply was made to PR kern/131743; it has been noted by GNATS. From: Elmar Stellnberger To: Jaakko Heinonen , bug-followup@freebsd.org Cc: Subject: Re: kern/131743: utf-8 file names of ext2 partitions cause problems Date: Wed, 18 Feb 2009 12:16:09 +0000 This is a multi-part message in MIME format. --------------060705010904020402090803 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Interestingly LC_ALL=en_US.UTF-8 works well with xterm, but with xterm only. All other apps from the ports tree like VLC or any KDE app like konsole or konqueror do not support utf-8. Perhaps we should reassign this bug to the ports project. Or do you think about a kernel charset conversion for filenames(iocharset=utf8) as an additional option? Jaakko Heinonen wrote: > On 2009-02-16, Elmar Stellnberger wrote: > >>> Class: sw-bug >>> > > >> FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and >> utf8 options. The consequence are not only wrongly displayed file >> names. >> > > I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8 > encoded file names providing that you have configured locale settings > correctly. > > Do you expect "iocharset=utf8" and "utf8" mount options to convert > file names to some other encoding? AFAIK even Linux doesn't support such > options for ext2. > > --------------060705010904020402090803 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Interestingly LC_ALL=en_US.UTF-8 works well with xterm, but with xterm only.
All other apps from the ports tree like VLC or any KDE app like konsole or konqueror
do not support utf-8. Perhaps we should reassign this bug to the ports project.

Or do you think about a kernel charset conversion for filenames(iocharset=utf8)
 as an additional option?


Jaakko Heinonen wrote: 
On 2009-02-16, Elmar Stellnberger wrote:
   
Class:          sw-bug
       

   
FreeBSD refuses to mount ext2 partitions with the iocharset=utf8 and
 utf8 options. The consequence are not only wrongly displayed file
 names.
     

 I don't think this is a bug. For me FreeBSD ext2fs works fine with UTF-8
 encoded file names providing that you have configured locale settings
 correctly.
 
 Do you expect "iocharset=utf8" and "utf8" mount options to convert
 file names to some other encoding? AFAIK even Linux doesn't support such
 options for ext2.

--------------060705010904020402090803-- From owner-freebsd-fs@FreeBSD.ORG Wed Feb 18 13:36:24 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 C79511065675; Wed, 18 Feb 2009 13:36:24 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9CCC68FC1C; Wed, 18 Feb 2009 13:36:24 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1IDaOgb039745; Wed, 18 Feb 2009 13:36:24 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1IDaOfb039741; Wed, 18 Feb 2009 13:36:24 GMT (envelope-from gavin) Date: Wed, 18 Feb 2009 13:36:24 GMT Message-Id: <200902181336.n1IDaOfb039741@freefall.freebsd.org> To: estellnb@gmail.com, gavin@FreeBSD.org, freebsd-fs@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/131743: [ext2fs] utf-8 file names of ext2 partitions cause problems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2009 13:36:25 -0000 Synopsis: [ext2fs] utf-8 file names of ext2 partitions cause problems State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Wed Feb 18 13:34:49 UTC 2009 State-Changed-Why: Close, this was a misconfiguration rather than a bug. http://www.freebsd.org/cgi/query-pr.cgi?pr=131743 From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 18:19: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 374BE106564A for ; Thu, 19 Feb 2009 18:19:49 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 22FBF8FC20 for ; Thu, 19 Feb 2009 18:19:49 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 541BA33C62; Thu, 19 Feb 2009 10:02:41 -0800 (PST) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id CA20D33C5B; Thu, 19 Feb 2009 10:02:40 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18845.40641.33220.936902@almost.alerce.com> Date: Thu, 19 Feb 2009 10:02:41 -0800 To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org X-Mailer: VM 8.0.12 under 22.1.50.1 (i386-apple-darwin8.11.1) X-Virus-Scanned: ClamAV using ClamSMTP Cc: goran.lowkrantz@ismobile.com, Pawel Jakub Dawidek Subject: Patch for 'zfs send -R' core dump (pr bin/130105) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 18:19:49 -0000 The following patch to /usr/src/sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c seems to keep 'zfs send -R' from dumping core. I've only been able to test sending the stream to /dev/null or a file, I'm still setting up a pool to do the receiving. This is based on a bit of gdb debugging and a thread from zfs-fuse: http://groups.google.com/group/zfs-fuse/browse_thread/thread/158cb78bc3325ae3/6a0109c7b0942707?#6a0109c7b0942707 g. --- zfs_prop.c 2009/02/17 18:58:58 1.1 +++ zfs_prop.c 2009/02/19 09:54:04 @@ -297,7 +297,7 @@ /* hidden properties */ register_hidden(ZFS_PROP_CREATETXG, "createtxg", PROP_TYPE_NUMBER, - PROP_READONLY, ZFS_TYPE_DATASET, NULL); + PROP_READONLY, ZFS_TYPE_DATASET, "CREATETXG"); register_hidden(ZFS_PROP_NUMCLONES, "numclones", PROP_TYPE_NUMBER, PROP_READONLY, ZFS_TYPE_SNAPSHOT, NULL); register_hidden(ZFS_PROP_NAME, "name", PROP_TYPE_STRING, From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 18:29: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 206AA10656E0 for ; Thu, 19 Feb 2009 18:29:54 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id C7EBF8FC12 for ; Thu, 19 Feb 2009 18:29:53 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 930B59CB15D; Thu, 19 Feb 2009 19:11:17 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hws6gqYwACZS; Thu, 19 Feb 2009 19:11:15 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 497349CB16C; Thu, 19 Feb 2009 19:11:15 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n1JIBE9A057623; Thu, 19 Feb 2009 19:11:14 +0100 (CET) (envelope-from rdivacky) Date: Thu, 19 Feb 2009 19:11:14 +0100 From: Roman Divacky To: George Hartzell Message-ID: <20090219181114.GA57360@freebsd.org> References: <18845.40641.33220.936902@almost.alerce.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18845.40641.33220.936902@almost.alerce.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, goran.lowkrantz@ismobile.com, freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: Patch for 'zfs send -R' core dump (pr bin/130105) 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, 19 Feb 2009 18:29:54 -0000 btw.... I track the opensolaris hg at work and there's a quite a few commits to zfs (almost) every week. fixing coredumps and other problems. maybe we can track the opensolaris a little closer? On Thu, Feb 19, 2009 at 10:02:41AM -0800, George Hartzell wrote: > > The following patch to > > /usr/src/sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c > > seems to keep 'zfs send -R' from dumping core. I've only been able to > test sending the stream to /dev/null or a file, I'm still setting up a > pool to do the receiving. > > This is based on a bit of gdb debugging and a thread from zfs-fuse: > > http://groups.google.com/group/zfs-fuse/browse_thread/thread/158cb78bc3325ae3/6a0109c7b0942707?#6a0109c7b0942707 > > g. > > --- zfs_prop.c 2009/02/17 18:58:58 1.1 > +++ zfs_prop.c 2009/02/19 09:54:04 > @@ -297,7 +297,7 @@ > > /* hidden properties */ > register_hidden(ZFS_PROP_CREATETXG, "createtxg", PROP_TYPE_NUMBER, > - PROP_READONLY, ZFS_TYPE_DATASET, NULL); > + PROP_READONLY, ZFS_TYPE_DATASET, "CREATETXG"); > register_hidden(ZFS_PROP_NUMCLONES, "numclones", PROP_TYPE_NUMBER, > PROP_READONLY, ZFS_TYPE_SNAPSHOT, NULL); > register_hidden(ZFS_PROP_NAME, "name", PROP_TYPE_STRING, > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 18: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 4B4A2106566B for ; Thu, 19 Feb 2009 18: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 39E058FC08 for ; Thu, 19 Feb 2009 18: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 n1JIe3aq087538 for ; Thu, 19 Feb 2009 18:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1JIe3Ep087537; Thu, 19 Feb 2009 18:40:03 GMT (envelope-from gnats) Date: Thu, 19 Feb 2009 18:40:03 GMT Message-Id: <200902191840.n1JIe3Ep087537@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: George Hartzell Cc: Subject: Re: bin/130105: [zfs] zfs send -R dumps core X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: George Hartzell List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 18:40:03 -0000 The following reply was made to PR bin/130105; it has been noted by GNATS. From: George Hartzell To: bug-followup@FreeBSD.org, goran.lowkrantz@ismobile.com Cc: Subject: Re: bin/130105: [zfs] zfs send -R dumps core Date: Thu, 19 Feb 2009 10:05:27 -0800 The following patch seems to fix the core dumps. I've only tested sending the stream to /dev/null and to a file, still working on setting up a receiver. This is based on a thread in the zfs-fuse mailing list. g. --- zfs_prop.c 2009/02/17 18:58:58 1.1 +++ zfs_prop.c 2009/02/19 09:54:04 @@ -297,7 +297,7 @@ /* hidden properties */ register_hidden(ZFS_PROP_CREATETXG, "createtxg", PROP_TYPE_NUMBER, - PROP_READONLY, ZFS_TYPE_DATASET, NULL); + PROP_READONLY, ZFS_TYPE_DATASET, "CREATETXG"); register_hidden(ZFS_PROP_NUMCLONES, "numclones", PROP_TYPE_NUMBER, PROP_READONLY, ZFS_TYPE_SNAPSHOT, NULL); register_hidden(ZFS_PROP_NAME, "name", PROP_TYPE_STRING, From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 21:04:22 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 1588C10656C6; Thu, 19 Feb 2009 21:04:22 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206045082.chello.pl [87.206.45.82]) by mx1.freebsd.org (Postfix) with ESMTP id BFFCA8FC1D; Thu, 19 Feb 2009 21:04:20 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 04118456AB; Thu, 19 Feb 2009 21:35:16 +0100 (CET) Received: from localhost (chello087206045082.chello.pl [87.206.45.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id E450645685; Thu, 19 Feb 2009 21:35:09 +0100 (CET) Date: Thu, 19 Feb 2009 21:35:41 +0100 From: Pawel Jakub Dawidek To: Roman Divacky Message-ID: <20090219203541.GB2083@garage.freebsd.pl> References: <18845.40641.33220.936902@almost.alerce.com> <20090219181114.GA57360@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vGgW1X5XWziG23Ko" Content-Disposition: inline In-Reply-To: <20090219181114.GA57360@freebsd.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, goran.lowkrantz@ismobile.com, freebsd-current@freebsd.org Subject: Re: Patch for 'zfs send -R' core dump (pr bin/130105) 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, 19 Feb 2009 21:04:22 -0000 --vGgW1X5XWziG23Ko Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 19, 2009 at 07:11:14PM +0100, Roman Divacky wrote: >=20 > btw.... I track the opensolaris hg at work and there's a quite a few comm= its > to zfs (almost) every week. fixing coredumps and other problems. >=20 > maybe we can track the opensolaris a little closer? It is beeing tracked very close, I'd say, in perforce (//depot/user/pjd/zfs/...). The problem is that trivial fixes are mixed with very intrusive changes, so it is too risky to track it even in HEAD (I'm running HEAD on my ZFS-only laptop!). OpenSolaris development is also very different from FreeBSD's. We use to describe every single change very carefully in commit logs, where OpenSolaris commits are based only on bug number and bug descriptions. Many changes are committed at once, so it is hard to pick only some changes. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --vGgW1X5XWziG23Ko Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFJncKcForvXbEpPzQRAgXhAKDf5XViG1Dp9qhZLW6NKUPL9bJXXwCgsfCn XJahA62CiDpUGk5jmzg45Eg= =H+Gt -----END PGP SIGNATURE----- --vGgW1X5XWziG23Ko-- From owner-freebsd-fs@FreeBSD.ORG Fri Feb 20 00:44:45 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA367106564A; Fri, 20 Feb 2009 00:44:45 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id BFE638FC08; Fri, 20 Feb 2009 00:44:45 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 8640A33C62; Thu, 19 Feb 2009 16:44:45 -0800 (PST) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id F1E3433C5B; Thu, 19 Feb 2009 16:44:44 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18845.64765.71312.244570@almost.alerce.com> Date: Thu, 19 Feb 2009 16:44:45 -0800 To: Pawel Jakub Dawidek In-Reply-To: <20090219203541.GB2083@garage.freebsd.pl> References: <18845.40641.33220.936902@almost.alerce.com> <20090219181114.GA57360@freebsd.org> <20090219203541.GB2083@garage.freebsd.pl> X-Mailer: VM 8.0.12 under 22.1.50.1 (i386-apple-darwin8.11.1) X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-fs@freebsd.org, goran.lowkrantz@ismobile.com, Roman Divacky , freebsd-current@freebsd.org Subject: Re: Patch for 'zfs send -R' core dump (pr bin/130105) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2009 00:44:46 -0000 Pawel Jakub Dawidek writes: > On Thu, Feb 19, 2009 at 07:11:14PM +0100, Roman Divacky wrote: > > > > btw.... I track the opensolaris hg at work and there's a quite a few commits > > to zfs (almost) every week. fixing coredumps and other problems. > > > > maybe we can track the opensolaris a little closer? > > It is beeing tracked very close, I'd say, in perforce > (//depot/user/pjd/zfs/...). > > The problem is that trivial fixes are mixed with very intrusive changes, > so it is too risky to track it even in HEAD (I'm running HEAD on my > ZFS-only laptop!). OpenSolaris development is also very different from > FreeBSD's. We use to describe every single change very carefully in > commit logs, where OpenSolaris commits are based only on bug number and > bug descriptions. Many changes are committed at once, so it is hard to > pick only some changes. Is it possible for fixes like the one that I posted to get merged into -CURRENT w/out waiting for your next mega-relase? On the one hand it would be very useful, on the other I can imagine that if it happens too often it would make your life difficult. g.