From bryanalves at gmail.com Thu Jan 1 06:05:02 2009 From: bryanalves at gmail.com (Bryan Alves) Date: Thu Jan 1 06:05:09 2009 Subject: NFS locking problems with 7.0-RELEASE In-Reply-To: References: <92f477740812291739o7c0b840bsd1cce4375577c41f@mail.gmail.com> <92f477740812301246k7ed77511oc969c22a3b5aad4d@mail.gmail.com> Message-ID: <92f477740812312205x554f06bbj4b3f7dcdbeb052f3@mail.gmail.com> On Wed, Dec 31, 2008 at 2:16 PM, Rick Macklem wrote: > > > On Tue, 30 Dec 2008, Bryan Alves wrote: > > - Download my server patches (ftp.cis.uoguelph.ca/pub/nfsv4/FreeBSD7) and >>> switch to using nfsv4, which has integral locking in the protocol. >>> >>> Have a good holiday, rick >>> >>> >>> Is there another location where I can get the nfs4 patches? That FTP >> seems >> to be down. >> >> Seems to be working here. Just "ftp ftp.cis.uoguelph.ca", login > "anonymous", then "cd pub/nfsv4/FreeBSD7". (Is it that you can't find > the machine? It's IP# is 131.104.48.112.) > > Also, outside the scope of this list, but since the discussion is opened, >> I >> might as well ask: >> >> If this NFS is the only remote mount that involves writing (it's opened >> read-only in other locations), and it's read/write locally, is it safe to >> use local locking? >> >> Yes, I believe so. Even if there are multiple clients rw mounting a file > system, local locking should be fine unless there are multiple clients > writing the same file in the file system. (With a single writer and > multiple readers, an application might run into coherency problems if > that application was written to use byte range locking to maintain > coherency (ie. most recently written data visible to the readers), but > that seems unlikely to matter for most applications/environments. (And > I'm not sure if the NLM is wired into NFS is such a way as to maintain > full coherency for the locked byte ranges anyhow, since normally NFS > does not maintain full coherency?) > > Have a happy new years, rick > > Well, I've upgraded to 7.1-RC2, in hopes that the kernel NFSLOCKD would make things better. Instead it made things worse. Now when locking fails, the system completely freezes, forcing a hard reset. There doesn't seem to be a way to turn off the kernel option anymore either (if you don't compile it in it's loaded on demand, and if it's not available because you move it, the kernel dies). I had some success turning off PF completely in getting NFS working, but even that has stopped now. I no longer have any idea what the problem is, nor do I have any other directions to diagnose it. Having the system completely lock up now makes most debugging efforts take extra long and makes them be a waste of time. I'm just going back to samba. I'll give up 20+ MB/s of throughput to have a working network-mounted home directory. From linimon at FreeBSD.org Fri Jan 2 05:53:01 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Fri Jan 2 05:53:07 2009 Subject: bin/130105: [zfs] zfs send -R dumps core Message-ID: <200901020553.n025r0L7093706@freefall.freebsd.org> Old Synopsis: [zfs] send -R dumpes core New Synopsis: [zfs] zfs send -R dumps core Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jan 2 05:52:37 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130105 From rwatson at FreeBSD.rg Fri Jan 2 11:27:06 2009 From: rwatson at FreeBSD.rg (Robert Watson) Date: Fri Jan 2 11:27:13 2009 Subject: Headers files included by vnode.h In-Reply-To: <20081223201626.caa483ad@mail01.compvia.com> References: <20081223201626.caa483ad@mail01.compvia.com> Message-ID: On Tue, 23 Dec 2008, Gerry Weaver wrote: > Perfect. Yes, I am building a kernel module. This is exactly what I was > looking for. I really appreciate your help. > > I am also trying to figure out a zero copy approach to kernel memory access > from user space. Would you happen to know which list I should post the > question to? Hi Gerry: It depends a bit what you want to accomplish with zero-copy. Are you just looking for a temporary mapping into kernel space for a user page, or a mapping of a kernel page into userspace? Is it only for use by privileged processes, or is this general-purpose? There are a number of concerns to think about, such as where the page comes from, whether leaked information that might also be present in the same page, if allocated from a general user of kernel pool, might be an issue, and how to tell when you're done with the page. If you just want a kernel facility to borrow a page from a user process temporarily, take a look at src/sys/net/bpf_zerocopy.c in 8.x, which borrows a set of user pages to use in-kernel for the duration of a BPF session. Robert N M Watson Computer Laboratory University of Cambridge From dfr at rabson.org Fri Jan 2 13:17:05 2009 From: dfr at rabson.org (Doug Rabson) Date: Fri Jan 2 13:17:14 2009 Subject: Booting from ZFS raidz In-Reply-To: <494F6C21.2000801@tzim.net> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <2F0DF92C-4240-48D4-9A5F-8B826D6D6E95@rabson.org> <87E89284-D3BF-4A5A-B6F7-C30709A3F2D9@lassitu.de> <4AC3BEB2-B47E-4280-85E1-C72891412D09@rabson.org> <494F6C21.2000801@tzim.net> Message-ID: <459358DB-15A6-4E27-A99E-D76A2A7DC73F@rabson.org> On 22 Dec 2008, at 10:29, Arnaud Houdelette wrote: > As I'm fairly interrested in this kind of setup, I set up a virtual > machine (VirtualBox) with 3 HD. > Sources are from a fresh current (csup yesterday). Applied your > patch successfully. > > Done a make installworld / installkernel to the zfs root. > Applied the bootcode as Stephan. > > The seem's the loader gets loaded, but it cant proceed further. > I got those kind of errors : I'm going to have to try and reproduce this but it looks as if you make have installed a gptzfsboot which doesn't include the raidz support. From jh at saunalahti.fi Sat Jan 3 18:21:10 2009 From: jh at saunalahti.fi (Jaakko Heinonen) Date: Sat Jan 3 18:21:18 2009 Subject: [patch] ext2fs freeze/corruption on amd64 Message-ID: <20090103182107.GA4119@a91-153-125-115.elisa-laajakaista.fi> Hi, I can quite easily reproduce a hard freeze while writing to an ext2fs filesystem on amd64. I can reliably reproduce it by building a kernel with "make -j2" on ext2fs. This has been reported by other people too: http://lists.freebsd.org/pipermail/freebsd-fs/2008-March/004504.html http://lists.freebsd.org/pipermail/freebsd-bugs/2008-January/027555.html http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/119529 http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/99561 I tracked the problem down to find_next_zero_bit() in ext2_bitops.h. The bug doesn't affect i386 because it uses asm bitops from i386-bitops.h. (There's also sparc64-bitops.h file but it's not used anywhere.) The problem is that if the offset (ofs) has one or more of it's five low bits set those bits are incorrectly re-added to the result. With following patch applied I can't reproduce the problem. %%% Index: sys/gnu/fs/ext2fs/ext2_bitops.h =================================================================== --- sys/gnu/fs/ext2fs/ext2_bitops.h (revision 186639) +++ sys/gnu/fs/ext2fs/ext2_bitops.h (working copy) @@ -84,7 +84,7 @@ find_next_zero_bit(void *data, size_t sz mask = ~0U << (ofs & 31); bit = *p | ~mask; if (bit != ~0U) - return (ffs(~bit) + ofs - 1); + return (ffs(~bit) + (ofs & ~31U) - 1); p++; ofs = (ofs + 31U) & ~31U; } %%% I hope that someone would commit this or similar fix. It might be also reasonable to delete the unused sparc64-bitops.h file. -- Jaakko From kostikbel at gmail.com Sun Jan 4 16:00:48 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Sun Jan 4 16:00:55 2009 Subject: [patch] ext2fs freeze/corruption on amd64 In-Reply-To: <20090103182107.GA4119@a91-153-125-115.elisa-laajakaista.fi> References: <20090103182107.GA4119@a91-153-125-115.elisa-laajakaista.fi> Message-ID: <20090104160043.GI93900@deviant.kiev.zoral.com.ua> On Sat, Jan 03, 2009 at 08:21:08PM +0200, Jaakko Heinonen wrote: > > Hi, > > I can quite easily reproduce a hard freeze while writing to an ext2fs > filesystem on amd64. I can reliably reproduce it by building a kernel > with "make -j2" on ext2fs. > > This has been reported by other people too: > > http://lists.freebsd.org/pipermail/freebsd-fs/2008-March/004504.html > http://lists.freebsd.org/pipermail/freebsd-bugs/2008-January/027555.html > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/119529 > http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/99561 > > I tracked the problem down to find_next_zero_bit() in ext2_bitops.h. > The bug doesn't affect i386 because it uses asm bitops from > i386-bitops.h. (There's also sparc64-bitops.h file but it's not used > anywhere.) > > The problem is that if the offset (ofs) has one or more of it's five low > bits set those bits are incorrectly re-added to the result. With > following patch applied I can't reproduce the problem. > > %%% > Index: sys/gnu/fs/ext2fs/ext2_bitops.h > =================================================================== > --- sys/gnu/fs/ext2fs/ext2_bitops.h (revision 186639) > +++ sys/gnu/fs/ext2fs/ext2_bitops.h (working copy) > @@ -84,7 +84,7 @@ find_next_zero_bit(void *data, size_t sz > mask = ~0U << (ofs & 31); > bit = *p | ~mask; > if (bit != ~0U) > - return (ffs(~bit) + ofs - 1); > + return (ffs(~bit) + (ofs & ~31U) - 1); > p++; > ofs = (ofs + 31U) & ~31U; > } > %%% > > I hope that someone would commit this or similar fix. It might be also > reasonable to delete the unused sparc64-bitops.h file. Please note that find_next_zero_bit() uses gcc extension to perform void-pointer arithmetic. Also, at the +2 line, it performs unaligned access to the uint32_t entities. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090104/33428f73/attachment.pgp From Sales at 1stChoiceAuctions.net Sun Jan 4 23:22:29 2009 From: Sales at 1stChoiceAuctions.net (Gareth) Date: Sun Jan 4 23:22:37 2009 Subject: auctions Message-ID: <20090104230353.TQPR19141.eastrmmtao102.cox.net@eastrmimpo01.cox.net> Skipped content of type multipart/related From jh at saunalahti.fi Mon Jan 5 07:50:14 2009 From: jh at saunalahti.fi (Jaakko Heinonen) Date: Mon Jan 5 07:50:25 2009 Subject: [patch] ext2fs freeze/corruption on amd64 In-Reply-To: <20090104160043.GI93900@deviant.kiev.zoral.com.ua> References: <20090103182107.GA4119@a91-153-125-115.elisa-laajakaista.fi> <20090104160043.GI93900@deviant.kiev.zoral.com.ua> Message-ID: <20090105075009.GB7863@a91-153-125-115.elisa-laajakaista.fi> On 2009-01-04, Kostik Belousov wrote: > Please note that find_next_zero_bit() uses gcc extension to perform > void-pointer arithmetic. Also, at the +2 line, it performs unaligned > access to the uint32_t entities. 76 find_next_zero_bit(void *data, size_t sz, size_t ofs) 77 { 78 uint32_t *p; 79 uint32_t mask; 80 int bit; 81 82 p = (uint32_t*)data + (ofs >> 5); Hmmm, I don't think so. Did you notice that the type of p is uint32_t * (line 78) and that data is casted to uint32_t * for pointer arithmetic (line 82)? Thank you for looking at this. -- Jaakko From bugmaster at FreeBSD.org Mon Jan 5 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 5 11:07:56 2009 Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org Message-ID: <200901051106.n05B6pFh002772@freefall.freebsd.org> 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 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 ex o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129084 fs [udf] [panic] udf panic: getblk: size(67584) > MAXBSIZ f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad o 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 o 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 ca o 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 30 problems total. From kostikbel at gmail.com Mon Jan 5 15:52:10 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Mon Jan 5 15:52:16 2009 Subject: [patch] ext2fs freeze/corruption on amd64 In-Reply-To: <20090105075009.GB7863@a91-153-125-115.elisa-laajakaista.fi> References: <20090103182107.GA4119@a91-153-125-115.elisa-laajakaista.fi> <20090104160043.GI93900@deviant.kiev.zoral.com.ua> <20090105075009.GB7863@a91-153-125-115.elisa-laajakaista.fi> Message-ID: <20090105155203.GN93900@deviant.kiev.zoral.com.ua> On Mon, Jan 05, 2009 at 09:50:10AM +0200, Jaakko Heinonen wrote: > On 2009-01-04, Kostik Belousov wrote: > > Please note that find_next_zero_bit() uses gcc extension to perform > > void-pointer arithmetic. Also, at the +2 line, it performs unaligned > > access to the uint32_t entities. > > 76 find_next_zero_bit(void *data, size_t sz, size_t ofs) > 77 { > 78 uint32_t *p; > 79 uint32_t mask; > 80 int bit; > 81 > 82 p = (uint32_t*)data + (ofs >> 5); > > Hmmm, I don't think so. Did you notice that the type of p is uint32_t * > (line 78) and that data is casted to uint32_t * for pointer arithmetic > (line 82)? You are right, I misparsed that line. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090105/710663ea/attachment.pgp From kgysmits at gmail.com Mon Jan 5 20:46:31 2009 From: kgysmits at gmail.com (Koen Smits) Date: Mon Jan 5 20:46:38 2009 Subject: FreeBSD, SSD's and partition alignment Message-ID: Hello all, I'm building a new NAS for home use and want to use a CompactFlash card for initial boot, ZFS for the rest. While doing some research on Flash based media performance, i stumbled on the following. Flash based media uses cells which are very often bigger than the usual HDD 512 Byte sector. When you change even one bit in a cell, you have to read, modify, write the whole cell. Just like with RAID5. When using the normal MBR disk layout one could easily mess up the fs alignment when starting the first primary partition on the default 63th sector. In this situation, when a fs block occupies a part of two flash cells, and both have to be read and written. This is bad for performance and for flash cell wear. On almost all flash based media (and also many RAID controllers) performance suffers greatly if the fs blocks are misaligned with the media stripe/cells. Some CF cards for example compensate internally for this by starting the second cell on sector #63, but this is not common practice and standards don't exist. Some SSD's like the OCZ Core series and other jMicron JMF602 based SSD's don't like misaligned writes and choke up because writes not aligned to the flash cells ups the write time latency. In my limited testing I created an MBR partition layout on a Kingston Ultimate 266x 2GB CF card, using a starting sector of 2048 instead of the default 63. I accomplished this by using the free MS Vista recovery disk, as Vista and Win2008 Server use a default alignment of 1MB when creating a new primary partition. There really doesn't seem to be a lot of tools out there that can create and/or resize a partition while allowing you to set the starting sector exactly. I must admit I used the first solution that worked though. When installing i changed the partition type and added the default BootMgr, installed, etc. fdisk warned about the partition not starting on a cylinder boundary, this was to be expected. Upon rebooting after finishing the install, the FreeBSD BootMgr fails to boot and beeps when trying. Looks like a problem. I'd like to discuss this subject a bit if anyone's interested. - partition alignment seems to be a real problem with some of today's flash and RAID media. I think people need to know one could easily increase performance (and media wear!) as no one knows this problem exists. - Is GPT the only supported way of creating correctly aligned partitions? - Did I make any mistakes in the above example? I've had to read a lot about the low-level layout of storage media and it could be I messed something up. - Should FreeBSD offer the option of aligned partitions in sysinstall, or offer (easy) GPT partitioning? Some reading material for the interested: http://blogs.msdn.com/jimmymay/archive/2008/10/14/disk-partition-alignment-for-sql-server-slide-deck.aspx Also check out the link to the presentation. Sincerely, Koen From andrew at modulus.org Tue Jan 6 00:12:22 2009 From: andrew at modulus.org (Andrew Snow) Date: Tue Jan 6 00:12:29 2009 Subject: FreeBSD, SSD's and partition alignment In-Reply-To: References: Message-ID: <4962A1D6.4040508@modulus.org> > I'd like to discuss this subject a bit if anyone's interested. > - partition alignment seems to be a real problem with some of today's flash > and RAID media. I think people need to know one could easily increase > performance (and media wear!) as no one knows this problem exists. Thanks for your interesting post! In my humble opinion, FreeBSD should not worry about this problem for the following reasons: 1. Performance for random write I/O still sucks even when the sector boundary is correct. Doing something like untarring src or ports causes many small write I/Os, and it is simply a shortcoming of early generation flash controller technology that they erase and rewrite in large blocks. 2. This problem will go away when flash controller technology improves. Intel SSDs have already demonstrated they can have great performance *and* a small erase block size, mitigating the issue completely. This technology will trickle down to the cheaper flash SSDs over time. - Andrew From remko at FreeBSD.org Tue Jan 6 09:15:33 2009 From: remko at FreeBSD.org (remko@FreeBSD.org) Date: Tue Jan 6 09:15:44 2009 Subject: i386/130210: Error by check nullfs Message-ID: <200901060915.n069FWrV040038@freefall.freebsd.org> Synopsis: Error by check nullfs Responsible-Changed-From-To: freebsd-i386->freebsd-fs Responsible-Changed-By: remko Responsible-Changed-When: Tue Jan 6 09:15:32 UTC 2009 Responsible-Changed-Why: This feels like an user question, reassign to -fs tea http://www.freebsd.org/cgi/query-pr.cgi?pr=130210 From remko at FreeBSD.org Tue Jan 6 15:05:45 2009 From: remko at FreeBSD.org (remko@FreeBSD.org) Date: Tue Jan 6 15:05:57 2009 Subject: kern/130229: usermount fails on fs that need iconv Message-ID: <200901061505.n06F5iuC000393@freefall.freebsd.org> Synopsis: usermount fails on fs that need iconv Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: remko Responsible-Changed-When: Tue Jan 6 15:05:43 UTC 2009 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=130229 From yanefbsd at gmail.com Tue Jan 6 17:20:05 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Tue Jan 6 17:20:16 2009 Subject: kern/130229: usermount fails on fs that need iconv Message-ID: <200901061720.n06HK5lQ098805@freefall.freebsd.org> The following reply was made to PR kern/130229; it has been noted by GNATS. From: "Garrett Cooper" To: "Artyom Zuikov" <4ertus2@mail.ru> Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/130229: usermount fails on fs that need iconv Date: Tue, 6 Jan 2009 09:14:55 -0800 sysctl -n vfs.usermount says? Thanks, -Garrett From maxim at macomnet.ru Tue Jan 6 20:50:05 2009 From: maxim at macomnet.ru (Maxim Konovalov) Date: Tue Jan 6 20:50:12 2009 Subject: kern/130229: usermount fails on fs that need iconv Message-ID: <200901062050.n06Ko34x056838@freefall.freebsd.org> The following reply was made to PR kern/130229; it has been noted by GNATS. From: Maxim Konovalov To: Garrett Cooper Cc: bug-followup@freebsd.org Subject: Re: kern/130229: usermount fails on fs that need iconv Date: Tue, 6 Jan 2009 23:44:30 +0300 (MSK) > sysctl -n vfs.usermount says? That's about wellknown problem with the usermount -- *iconv.ko modules won't be loaded by non-root user. -- Maxim Konovalov From 4ertus2 at mail.ru Wed Jan 7 02:40:05 2009 From: 4ertus2 at mail.ru (4ertus2) Date: Wed Jan 7 02:40:12 2009 Subject: kern/130229: usermount fails on fs that need iconv Message-ID: <200901070240.n072e5k3025781@freefall.freebsd.org> The following reply was made to PR kern/130229; it has been noted by GNATS. From: 4ertus2 <4ertus2@mail.ru> To: "Garrett Cooper" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/130229: usermount fails on fs that need iconv Date: Wed, 7 Jan 2009 04:59:01 +0300 > sysctl -n vfs.usermount says? ~> sysctl -n vfs.usermount 1 The problem looks like FreeBSD tryes to load *iconv modules the first time I mount filesystem, but user have't permitions for this operation. In this case kldload should have an option to load modules immediately. From mjguzik at gmail.com Wed Jan 7 03:20:04 2009 From: mjguzik at gmail.com (Mateusz Guzik) Date: Wed Jan 7 03:20:14 2009 Subject: kern/130229: [iconv] usermount fails on fs that need iconv Message-ID: <200901070320.n073K3di055301@freefall.freebsd.org> The following reply was made to PR kern/130229; it has been noted by GNATS. From: Mateusz Guzik To: bug-followup@freebsd.org Cc: Subject: Re: kern/130229: [iconv] usermount fails on fs that need iconv Date: Wed, 7 Jan 2009 04:10:39 +0100 Hi, this is a duplicate of kern/109024. As described, mount_msdosfs calls kiconv_add_xlat16_cspairs and it fails. While mounting using root credentials, kiconv_add_xlat16_cspairs is successfull and that's why after mount/umount it works fine for non-root users. bin/93857 contains possible fix. Thanks, -- Mateusz Guzik From kgysmits at gmail.com Wed Jan 7 12:54:53 2009 From: kgysmits at gmail.com (Koen Smits) Date: Wed Jan 7 12:54:58 2009 Subject: FreeBSD, SSD's and partition alignment In-Reply-To: <4962A1D6.4040508@modulus.org> References: <4962A1D6.4040508@modulus.org> Message-ID: On Tue, Jan 6, 2009 at 01:12, Andrew Snow wrote: > I'd like to discuss this subject a bit if anyone's interested. >> - partition alignment seems to be a real problem with some of today's >> flash >> and RAID media. I think people need to know one could easily increase >> performance (and media wear!) as no one knows this problem exists. >> > > Thanks for your interesting post! > > In my humble opinion, FreeBSD should not worry about this problem for the > following reasons: > > 1. Performance for random write I/O still sucks even when the sector > boundary is correct. Doing something like untarring src or ports causes > many small write I/Os, and it is simply a shortcoming of early generation > flash controller technology that they erase and rewrite in large blocks. > > 2. This problem will go away when flash controller technology improves. > Intel SSDs have already demonstrated they can have great performance *and* > a small erase block size, mitigating the issue completely. This technology > will trickle down to the cheaper flash SSDs over time. > > > - Andrew > Sorry for the late reply. I've been busy. I agree with point 1, if the controller is able to 'save up' small writes and write this sequentially without making a mess out of it, this is preferred. We will never completely remove the 'virtual layers' between the OS and the storage medium itself and that is fine. point 2 however, i disagree. It's time we dump the whole track/cylinder/head thing. Even back in 1984 this was already outdated, lets just throw it overboard! Let's assume that from FreeBSD 8 and onward, we just use GPT and a partition offset of 1MB by default. Everybody would benefit, and no-one would really have any problems with it, right? We would all benefit in my opinion. Note that even the Intel X25-M series seem to slow down in random write speed when the complete disk is filled and there are no cells left that the controller knows are free. Most benchmarks out there are run on an empty Intel SSD. When you rerun that test several times, it'll slowly settle on a much lower random write speed. From andrew at modulus.org Wed Jan 7 23:28:15 2009 From: andrew at modulus.org (Andrew Snow) Date: Wed Jan 7 23:28:22 2009 Subject: iscsi client hangs performing I/O on a dead target In-Reply-To: References: <6c1e076a0901070247l7c006efajda8fddee84c337a@mail.gmail.com> Message-ID: <49653A7D.30906@modulus.org> Danny Braniss wrote: > freebsd likes to > panic if a disc goes away, so don't hold your breath for a solution soon. You hit the nail on the head. This is going to be a increasingly bad problem as we continue pushing in this of networked storage. It would be REALLY nice, if an I/O fails, to simply have the process attempting the I/O to be killed, instead of bringing the machine to its knees and locking up or panic the kernel. - Andrew From fbsd at dannysplace.net Thu Jan 8 01:11:02 2009 From: fbsd at dannysplace.net (Danny Carroll) Date: Thu Jan 8 01:11:09 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <20081117070818.GA22231@icarus.home.lan> References: <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> <490A8FAD.8060009@dannysplace.net> <491BBF38.9010908@dannysplace.net> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> Message-ID: <496549D9.7010003@dannysplace.net> I'd like to post some results of what I have found with my tests. I did a few different types of tests. Basically a set of 5-disk tests and a set of 12-disk tests. I did this because I only had 5 ports available on my onboard controller and I wanted to see how the areca compared to that. I also wanted to see comparisons between JBOD, Passthru and hardware raid5. I have not tested raid6 or raidz2. You can see the results here: http://www.dannysplace.net/quickweb/filesystem%20tests.htm An explanation of each of the tests: ICH9_ZFS 5 disk zfs raidz test with onboard SATA ports. ARECAJBOD_ZFS 5 disk zfs raidz test with Areca SATA ports configured in JBOD mode. ARECAJBOD_ZFS_NoWriteCache 5 disk zfs raidz test with Areca SATA ports configured in JBOD mode and with disk caches disabled. ARECARAID 5 disk zfs single-disk test with Areca raid5 array. ARECAPASSTHRU 5 disk zfs raidz test with Areca SATA ports configured in Passthru mode. This means that the onboard areca cache is active. ARECARAID-UFS2 5 disk ufs2 single-disk test with Areca raid5 array. ARECARAID-BIG 12 disk zfs single-disk test with Areca raid5 array. ARECAPASSTHRU_12 12 disk zfs raidz test with Areca SATA ports configured in Passthru mode. This means that the onboard areca cache is active. I'll probably be opting for the ARECAPASSTHRU_12 configuration. Mainly because I do not need amazing read speeds (network port would be saturated anyway) and I think that the raidz implementation would be more fault tolerant. By that I mean if you have a disk read error during a rebuild then as I understand it, raidz will write off that block (and hopefully tell me about dead files) but continue with the rest of the rebuild. This is something I'd love to test for real, just to see what happens. But I am not sure how I could do that. Perhaps removing one drive, then a few random writes to a remaining disk (or two) and seeing how it goes with a rebuild. Something else worth mentioning. When I converted from JBOD to passthrough, I was able to re-import the disks without any problems. This must mean that the areca passthrough option does not alter the disk much, perhaps not at all. After a 21 hour rebuild I have to say I am not that keen to do more of these tests, but if there is something someone wants to see, then I'll definitely consider it. One thing I am at a loss to understand is why turning off the disk caches when testing the JBOD performance produced almost identical (very slightly better) results. Perhaps it was a case of the ZFS internal cache making the disks cache redundant? Comparing to the ARECA passthrough (where the areca cache is used) shows again, similar results. -D From zbeeble at gmail.com Thu Jan 8 07:40:38 2009 From: zbeeble at gmail.com (Zaphod Beeblebrox) Date: Thu Jan 8 07:40:45 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <496549D9.7010003@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <490A8FAD.8060009@dannysplace.net> <491BBF38.9010908@dannysplace.net> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> Message-ID: <5f67a8c40901072340u1dd514b4x21506d4ca491ff6d@mail.gmail.com> On Wed, Jan 7, 2009 at 7:33 PM, Danny Carroll wrote: > I'd like to post some results of what I have found with my tests. > I did a few different types of tests. Basically a set of 5-disk tests > and a set of 12-disk tests. > > I did this because I only had 5 ports available on my onboard controller > and I wanted to see how the areca compared to that. I also wanted to > see comparisons between JBOD, Passthru and hardware raid5. > > I have not tested raid6 or raidz2. > > You can see the results here: > http://www.dannysplace.net/quickweb/filesystem%20tests.htm > ... been a long time since I've seen someone link stuff on this list that won't shot in Firefox. Pretty sad that it's just a table of values that would be just as well presented as text. From kgysmits at gmail.com Thu Jan 8 07:48:37 2009 From: kgysmits at gmail.com (Koen Smits) Date: Thu Jan 8 07:48:43 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <496549D9.7010003@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <490A8FAD.8060009@dannysplace.net> <491BBF38.9010908@dannysplace.net> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> Message-ID: > One thing I am at a loss to understand is why turning off the disk > caches when testing the JBOD performance produced almost identical (very > slightly better) results. Perhaps it was a case of the ZFS internal > cache making the disks cache redundant? Comparing to the ARECA > passthrough (where the areca cache is used) shows again, similar results. > > -D > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" My guess is it probably has to do with the way ZFS does cache flushes: http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Cache_Flushes It might be worth it to disable the forced flushing and test again, if you feel like it. -Koen From peterjeremy at optushome.com.au Thu Jan 8 09:37:54 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Thu Jan 8 09:38:06 2009 Subject: iscsi client hangs performing I/O on a dead target In-Reply-To: <49653A7D.30906@modulus.org> References: <6c1e076a0901070247l7c006efajda8fddee84c337a@mail.gmail.com> <49653A7D.30906@modulus.org> Message-ID: <20090108071749.GM87057@server.vk2pj.dyndns.org> On 2009-Jan-08 10:27:57 +1100, Andrew Snow wrote: >It would be REALLY nice, if an I/O fails, to simply have the process >attempting the I/O to be killed, instead of bringing the machine to its >knees and locking up or panic the kernel. And if it was that easy, it would have been done about a decade ago. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090108/2db96918/attachment.pgp From ndenev at gmail.com Thu Jan 8 09:45:53 2009 From: ndenev at gmail.com (Nikolay Denev) Date: Thu Jan 8 09:45:59 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <496549D9.7010003@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <490A849C.7030009@dannysplace.net> <20081031043412.GA22289@icarus.home.lan> <490A8FAD.8060009@dannysplace.net> <491BBF38.9010908@dannysplace.net> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8 Jan, 2009, at 02:33 , Danny Carroll wrote: > I'd like to post some results of what I have found with my tests. > I did a few different types of tests. Basically a set of 5-disk tests > and a set of 12-disk tests. > > I did this because I only had 5 ports available on my onboard > controller > and I wanted to see how the areca compared to that. I also wanted to > see comparisons between JBOD, Passthru and hardware raid5. > > I have not tested raid6 or raidz2. > > You can see the results here: > http://www.dannysplace.net/quickweb/filesystem%20tests.htm > > An explanation of each of the tests: > ICH9_ZFS 5 disk zfs raidz test with onboard SATA > ports. > ARECAJBOD_ZFS 5 disk zfs raidz test with Areca SATA > ports configured in JBOD mode. > ARECAJBOD_ZFS_NoWriteCache 5 disk zfs raidz test with Areca SATA > ports configured in JBOD mode and with > disk caches disabled. > ARECARAID 5 disk zfs single-disk test with Areca > raid5 array. > ARECAPASSTHRU 5 disk zfs raidz test with Areca SATA ports > configured in Passthru mode. This > means that the onboard areca cache is > active. > ARECARAID-UFS2 5 disk ufs2 single-disk test with Areca > raid5 array. > ARECARAID-BIG 12 disk zfs single-disk test with Areca > raid5 array. > ARECAPASSTHRU_12 12 disk zfs raidz test with Areca SATA ports > configured in Passthru mode. This > means that the onboard areca cache is > active. > > > I'll probably be opting for the ARECAPASSTHRU_12 configuration. > Mainly > because I do not need amazing read speeds (network port would be > saturated anyway) and I think that the raidz implementation would be > more fault tolerant. By that I mean if you have a disk read error > during a rebuild then as I understand it, raidz will write off that > block (and hopefully tell me about dead files) but continue with the > rest of the rebuild. > > This is something I'd love to test for real, just to see what happens. > But I am not sure how I could do that. Perhaps removing one drive, > then > a few random writes to a remaining disk (or two) and seeing how it > goes > with a rebuild. > > Something else worth mentioning. When I converted from JBOD to > passthrough, I was able to re-import the disks without any problems. > This must mean that the areca passthrough option does not alter the > disk > much, perhaps not at all. > > After a 21 hour rebuild I have to say I am not that keen to do more of > these tests, but if there is something someone wants to see, then I'll > definitely consider it. > > One thing I am at a loss to understand is why turning off the disk > caches when testing the JBOD performance produced almost identical > (very > slightly better) results. Perhaps it was a case of the ZFS internal > cache making the disks cache redundant? Comparing to the ARECA > passthrough (where the areca cache is used) shows again, similar > results. > > -D > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" There is a big difference betweeen hardware and ZFS raidz with 12 disk on the get_block test, maybe it would be interesting to rerun this test with zfs prefetch disabled? - -- Regards, Nikolay Denev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (Darwin) iEYEARECAAYFAkllxT8ACgkQHNAJ/fLbfrnHnwCeJ8nSjBY6fc0Lvu2+fSN5E4HI zb0Ani2ZFLdxYCWYBuCnoo+D244O2lg5 =EKgi -----END PGP SIGNATURE----- From peter.schuller at infidyne.com Thu Jan 8 13:25:48 2009 From: peter.schuller at infidyne.com (Peter Schuller) Date: Thu Jan 8 13:25:55 2009 Subject: FreeBSD, SSD's and partition alignment In-Reply-To: References: <4962A1D6.4040508@modulus.org> Message-ID: <20090108132546.GA57786@hyperion.scode.org> > Note that even the Intel X25-M series seem to slow down in random write > speed when the complete disk is filled and there are no cells left that the > controller knows are free. Most benchmarks out there are run on an empty > Intel SSD. When you rerun that test several times, it'll slowly settle on a > much lower random write speed. My understanding is that the performance drop should only come from *sustained* high write iops; i.e., when you effectively exhaust the free space necessary to perform the writes sequentially but temporarily. But on the other hand if you are only bursting, I was under the impression these guys did background re-writing such that no permanent performance drop need be expected. Is this not the case for the X25-M or others? -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090108/413507f9/attachment.pgp From john at kozubik.com Thu Jan 8 15:14:23 2009 From: john at kozubik.com (John Kozubik) Date: Thu Jan 8 15:14:30 2009 Subject: 64-bit quota support now available for 6.x and 7.x Message-ID: <20090108065139.M61433@kozubik.com> Hello, Kirk McKusick has responded to the bounty I posted in June for 64-bit quota support in FreeBSD. He has provided patches for both 6.x and 7.x which I, and others, have tested. I am currently using them in a production environment at rsync.net. Full details: http://blog.kozubik.com/john_kozubik/2009/01/64bit-freebsd-quotas.html --- John Kozubik - john@kozubik.com - http://www.kozubik.com From kgysmits at gmail.com Thu Jan 8 15:31:53 2009 From: kgysmits at gmail.com (Koen Smits) Date: Thu Jan 8 15:32:00 2009 Subject: FreeBSD, SSD's and partition alignment In-Reply-To: <20090108132546.GA57786@hyperion.scode.org> References: <4962A1D6.4040508@modulus.org> <20090108132546.GA57786@hyperion.scode.org> Message-ID: I have not tested this to an extent that I can be sure this is the way it works. Sorry. On Thu, Jan 8, 2009 at 14:25, Peter Schuller wrote: > > Note that even the Intel X25-M series seem to slow down in random write > > speed when the complete disk is filled and there are no cells left that > the > > controller knows are free. Most benchmarks out there are run on an empty > > Intel SSD. When you rerun that test several times, it'll slowly settle on > a > > much lower random write speed. > > My understanding is that the performance drop should only come from > *sustained* high write iops; i.e., when you effectively exhaust the > free space necessary to perform the writes sequentially but > temporarily. But on the other hand if you are only bursting, I was > under the impression these guys did background re-writing such that no > permanent performance drop need be expected. > > Is this not the case for the X25-M or others? > > -- > / Peter Schuller > > PGP userID: 0xE9758B7D or 'Peter Schuller ' > Key retrieval: Send an E-Mail to getpgpkey@scode.org > E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org > > From freebsd at edvax.de Thu Jan 8 23:57:25 2009 From: freebsd at edvax.de (Polytropon) Date: Thu Jan 8 23:57:32 2009 Subject: Restore deleted files Message-ID: <20090109002846.c67d962f.freebsd@edvax.de> Hi, I'd like to ask a two-stage question: 1. Is it possible to recover files that have been deleted? 2. Which tools or procedures are suggested for recovery? While sorting out some files and transfering them to another hard disk, I accidentally deleted too much: the directory with my videos taken by a digital camera. They were located in a directory within a subtree, and I deleted the whole subtree without first copying these files. I used the Midnight Commander to do this. As I read from its source code, it seems to use the unlink() call to delete the subtree recursively. Pressing PF8 can really ruin your day... Just after I noticed what I had done I unmounted the file system, powered off the machine and put the disk on the shelf (it's still there), no further write accesses. I would be glad if someone could enlighten me if there is any chance to get the files back, even with the loss of the file names (doesn't matter), and which tools seem to serve best in this difficult task. And if it's impossible, please tell me. I can newfs the disk then and free it, along with my mind. PS. I'm posting this question to -fs, too. Answers from this list please keep me in CC because I'm not subscribed to -fs. Thank you! -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From julian at elischer.org Fri Jan 9 00:35:43 2009 From: julian at elischer.org (Julian Elischer) Date: Fri Jan 9 00:35:55 2009 Subject: Restore deleted files In-Reply-To: <20090109002846.c67d962f.freebsd@edvax.de> References: <20090109002846.c67d962f.freebsd@edvax.de> Message-ID: <49669529.4010501@elischer.org> Polytropon wrote: > Hi, > > I'd like to ask a two-stage question: > > 1. Is it possible to recover files that have been deleted? > > 2. Which tools or procedures are suggested for recovery? > > While sorting out some files and transfering them to another > hard disk, I accidentally deleted too much: the directory with > my videos taken by a digital camera. They were located in a > directory within a subtree, and I deleted the whole subtree > without first copying these files. > > I used the Midnight Commander to do this. As I read from its > source code, it seems to use the unlink() call to delete the > subtree recursively. Pressing PF8 can really ruin your day... > > Just after I noticed what I had done I unmounted the file system, > powered off the machine and put the disk on the shelf (it's still > there), no further write accesses. unmounting could have made things worse :-/ it then actually cleaned up and wrote the changes.... the best would have been to ahve hit and dropped into the debugger and then unplugged the drive.. still you MIGHT be lucky if the files are contiguous on disk (which images are likely to be. I don't know hte tools bu there are some... they are usually more useful for recovering from crashes etc. the trouble with accidental deletes is that they often leave no information as to what went where. hopefully someone else can give you more info as to tools. > > I would be glad if someone could enlighten me if there is any > chance to get the files back, even with the loss of the file > names (doesn't matter), and which tools seem to serve best in > this difficult task. > > And if it's impossible, please tell me. I can newfs the disk > then and free it, along with my mind. > > > > > PS. > I'm posting this question to -fs, too. Answers from this list > please keep me in CC because I'm not subscribed to -fs. Thank you! > From cswiger at mac.com Fri Jan 9 00:55:59 2009 From: cswiger at mac.com (Chuck Swiger) Date: Fri Jan 9 00:56:04 2009 Subject: Restore deleted files In-Reply-To: <20090109002846.c67d962f.freebsd@edvax.de> References: <20090109002846.c67d962f.freebsd@edvax.de> Message-ID: On Jan 8, 2009, at 3:28 PM, Polytropon wrote: > I'd like to ask a two-stage question: > > 1. Is it possible to recover files that have been deleted? > > 2. Which tools or procedures are suggested for recovery? The preferred method is to recover files from backup. If you don't take backups, you've decided that you don't really care about the data. This being said, you might take a look at something like: > % cat /usr/ports/sysutils/sleuthkit/pkg-descr > The Sleuth Kit (previously known as TASK) is a collection of UNIX- > based > command line file system and media management forensic analysis > tools. The > file system tools allow you to examine file systems of a suspect > computer in > a non-intrusive fashion. > > The media management tools allow you to examine the layout of disks > and > other media. The Sleuth Kit supports DOS partitions, BSD partitions > (disk > labels), Mac partitions, Sun slices (Volume Table of Contents), and > GPT > disks. With these tools, you can identify where partitions are > located and > extract them so that they can be analyzed with file system analysis > tools. > > WWW: http://www.sleuthkit.org/sleuthkit/ This can be used to attempt to "undelete" files from a UFS filesystem.... Regards, -- -Chuck From fbsd at dannysplace.net Fri Jan 9 02:30:22 2009 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jan 9 02:30:54 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: References: <20081031033208.GA21220@icarus.home.lan> <490A8FAD.8060009@dannysplace.net> <491BBF38.9010908@dannysplace.net> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> Message-ID: <4966B6B1.8020502@dannysplace.net> Koen Smits wrote: > My guess is it probably has to do with the way ZFS does cache flushes: > http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Cache_Flushes > It might be worth it to disable the forced flushing and test again, if > you feel like it. I've just done this and the results are on the same page: http://www.dannysplace.net/quickweb/filesystem%20tests.htm The Excel version is here: http://www.dannysplace.net/quickweb/filesystem%20tests.xls It is a major improvement but I do not know 100% for sure if the disks are protected by the write cache/battery backup when in Passthrough mode. When creating a passthrough disk the "Volume Cache Mode" can be set to "Write Back" or "Write Through". This makes me feel as though the cache is being used and that when the cache is used, so is the BBU. But I cannot be 100% sure. I will send an email to Areca support to ask. -D From kgysmits at gmail.com Fri Jan 9 08:46:59 2009 From: kgysmits at gmail.com (Koen Smits) Date: Fri Jan 9 08:47:12 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <4966B6B1.8020502@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> Message-ID: Those numbers are pretty good, right? Who needs onboard XOR anyway :) On Fri, Jan 9, 2009 at 03:30, Danny Carroll wrote: > Koen Smits wrote: > > My guess is it probably has to do with the way ZFS does cache flushes: > > > http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Cache_Flushes > > It might be worth it to disable the forced flushing and test again, if > > you feel like it. > > I've just done this and the results are on the same page: > > http://www.dannysplace.net/quickweb/filesystem%20tests.htm > The Excel version is here: > > http://www.dannysplace.net/quickweb/filesystem%20tests.xls > > It is a major improvement but I do not know 100% for sure if the disks > are protected by the write cache/battery backup when in Passthrough mode. > > When creating a passthrough disk the "Volume Cache Mode" can be set to > "Write Back" or "Write Through". This makes me feel as though the cache > is being used and that when the cache is used, so is the BBU. But I > cannot be 100% sure. I will send an email to Areca support to ask. > > -D > From fbsd at dannysplace.net Fri Jan 9 09:02:11 2009 From: fbsd at dannysplace.net (Danny Carroll) Date: Fri Jan 9 09:02:23 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: References: <20081031033208.GA21220@icarus.home.lan> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> Message-ID: <496712A2.4020800@dannysplace.net> Koen Smits wrote: > Those numbers are pretty good, right? Who needs onboard XOR anyway :) > Those numbers are great, but I would love to know that writes to the disks are also protected by the battery backup. If not then I'll be forced to use either hardware raid5/6 or perhaps some other configuration. Maybe 6 stripe sets in a raidz array? At the end of the day however I really don't care about the performance, even the slowest of the tests I did would be fast enough to saturate a gigabit ethernet port, which is way fast enough for me. But its an interesting set of tests... -D From kgysmits at gmail.com Fri Jan 9 15:58:07 2009 From: kgysmits at gmail.com (Koen Smits) Date: Fri Jan 9 15:58:13 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <496712A2.4020800@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> Message-ID: Please let us know what Areca says about the caching. If you ask me, these results definitely are cached. On Fri, Jan 9, 2009 at 10:02, Danny Carroll wrote: > Koen Smits wrote: > > Those numbers are pretty good, right? Who needs onboard XOR anyway :) > > > > Those numbers are great, but I would love to know that writes to the > disks are also protected by the battery backup. If not then I'll be > forced to use either hardware raid5/6 or perhaps some other > configuration. Maybe 6 stripe sets in a raidz array? > > At the end of the day however I really don't care about the performance, > even the slowest of the tests I did would be fast enough to saturate a > gigabit ethernet port, which is way fast enough for me. But its an > interesting set of tests... > > -D > From andrew at modulus.org Sat Jan 10 02:38:55 2009 From: andrew at modulus.org (Andrew Snow) Date: Sat Jan 10 02:39:03 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <496712A2.4020800@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <491C5AA7.1030004@samsco.org> <491C9535.3030504@dannysplace.net> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> Message-ID: <49680A26.1020502@modulus.org> ZFS does not require battery-backed disk cache, as long as disks and controller flush their cache when they are told to by the OS. Then ZFS only issues sync/flush commands for the ZIL (transaction log), but majority of I/Os are free to sit in cache to complete when they are ready. Data that is not fsync()'d by the application may be lost on power outage, but stuff like databases do fsync() so they are protected. - Andrew From fbsd at dannysplace.net Sat Jan 10 04:58:51 2009 From: fbsd at dannysplace.net (Danny Carroll) Date: Sat Jan 10 04:58:57 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: References: <20081031033208.GA21220@icarus.home.lan> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> Message-ID: <49682AEF.8010006@dannysplace.net> Koen Smits wrote: > Please let us know what Areca says about the caching. > If you ask me, these results definitely are cached. > Are yes but are they cached by the OS or by the array controller :-) -D From ndenev at gmail.com Sat Jan 10 11:56:46 2009 From: ndenev at gmail.com (Nikolay Denev) Date: Sat Jan 10 11:56:53 2009 Subject: Booting from ZFS raidz In-Reply-To: <459358DB-15A6-4E27-A99E-D76A2A7DC73F@rabson.org> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <2F0DF92C-4240-48D4-9A5F-8B826D6D6E95@rabson.org> <87E89284-D3BF-4A5A-B6F7-C30709A3F2D9@lassitu.de> <4AC3BEB2-B47E-4280-85E1-C72891412D09@rabson.org> <494F6C21.2000801@tzim.net> <459358DB-15A6-4E27-A99E-D76A2A7DC73F@rabson.org> Message-ID: <12C6C9A1-D4F0-442A-A92C-1B4565AEEAF8@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2 Jan, 2009, at 15:17 , Doug Rabson wrote: > > On 22 Dec 2008, at 10:29, Arnaud Houdelette wrote: > >> As I'm fairly interrested in this kind of setup, I set up a virtual >> machine (VirtualBox) with 3 HD. >> Sources are from a fresh current (csup yesterday). Applied your >> patch successfully. >> >> Done a make installworld / installkernel to the zfs root. >> Applied the bootcode as Stephan. >> >> The seem's the loader gets loaded, but it cant proceed further. >> I got those kind of errors : > > I'm going to have to try and reproduce this but it looks as if you > make have installed a gptzfsboot which doesn't include the raidz > support. > I have just tried installing the new gptzfsboot with a 7.1-STABLE install, but all i got is a : "No ZFS pools located, can't boot" message. I used 7.1-STABLE DVD, but I have copied and installed /boot/pmbr / boot/gptzfsboot and /boot/loader from a - -CURRENT system built with your patch and LOADER_ZFS_SUPPORT All my disks have valid guid partition tables with p1 of type freebsd- boot with installed pmbr and gptzfsboot from -CURRENT, and p2 partition of type freebsd-zfs with a valid pool that i can mount using LiveFS. Any suggestions? - -- Regards, Nikolay Denev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (Darwin) iEYEARECAAYFAklojPYACgkQHNAJ/fLbfrlBZgCfbD6m7KuyyZEJueYLirOi7GhX Nd0AoJrOB7t2n/KOtbECbMrrAMs0pxs9 =sEqt -----END PGP SIGNATURE----- From gtodd at bellanet.org Sun Jan 11 18:59:59 2009 From: gtodd at bellanet.org (Graham Todd) Date: Sun Jan 11 19:00:06 2009 Subject: iscsi client hangs performing I/O on a dead target Message-ID: <496AABFB.4060404@bellanet.org> Hi, I believe the FreeBSD foundation is supporting development that may help with this (the "Safe Removal of Active Disk Devices" project)? The focus is on USB devices since, as noted in the newsletter, "[t]he removable USB disk causing a crash turns out to be our #1 reported bug." :-) Hopefully the work can be useful in a generic way since panics induced by disappearing USB devices are easier to control than those caused by disappearing network storage. cheers, From: http://www.freebsdfoundation.org/press/2008Dec-newsletter.shtm ... [snip] ... The first project to get off the ground is to make FreeBSD tolerate the removal of active disk devices, such as when a USB flash device with a mounted filesystems is physically detached by a user. Currently the system may panic in this situation. The work involves adding proper reference counting to strategic portions of the kernel and modifying filesystems to properly handle "device lost" errors. Edward Tomasz Napierala is the developer working on this project. ... From ivoras at freebsd.org Mon Jan 12 01:35:03 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Jan 12 01:35:08 2009 Subject: iscsi client hangs performing I/O on a dead target In-Reply-To: <49653A7D.30906@modulus.org> References: <6c1e076a0901070247l7c006efajda8fddee84c337a@mail.gmail.com> <49653A7D.30906@modulus.org> Message-ID: Andrew Snow wrote: > Danny Braniss wrote: >> freebsd likes to >> panic if a disc goes away, so don't hold your breath for a solution soon. > > > You hit the nail on the head. This is going to be a increasingly bad > problem as we continue pushing in this of networked storage. > > It would be REALLY nice, if an I/O fails, to simply have the process > attempting the I/O to be killed, instead of bringing the machine to its > knees and locking up or panic the kernel. There have been some commits recently related to this problem - you could try running 8-CURRENT and see if it's addressed. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090112/2607d4b8/signature.pgp From ndenev at gmail.com Mon Jan 12 02:36:01 2009 From: ndenev at gmail.com (Nikolay Denev) Date: Mon Jan 12 02:36:13 2009 Subject: Booting from ZFS raidz In-Reply-To: <12C6C9A1-D4F0-442A-A92C-1B4565AEEAF8@gmail.com> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <2F0DF92C-4240-48D4-9A5F-8B826D6D6E95@rabson.org> <87E89284-D3BF-4A5A-B6F7-C30709A3F2D9@lassitu.de> <4AC3BEB2-B47E-4280-85E1-C72891412D09@rabson.org> <494F6C21.2000801@tzim.net> <459358DB-15A6-4E27-A99E-D76A2A7DC73F@rabson.org> <12C6C9A1-D4F0-442A-A92C-1B4565AEEAF8@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10 Jan, 2009, at 13:56 , Nikolay Denev wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On 2 Jan, 2009, at 15:17 , Doug Rabson wrote: > >> >> On 22 Dec 2008, at 10:29, Arnaud Houdelette wrote: >> >>> As I'm fairly interrested in this kind of setup, I set up a >>> virtual machine (VirtualBox) with 3 HD. >>> Sources are from a fresh current (csup yesterday). Applied your >>> patch successfully. >>> >>> Done a make installworld / installkernel to the zfs root. >>> Applied the bootcode as Stephan. >>> >>> The seem's the loader gets loaded, but it cant proceed further. >>> I got those kind of errors : >> >> I'm going to have to try and reproduce this but it looks as if you >> make have installed a gptzfsboot which doesn't include the raidz >> support. >> > > > I have just tried installing the new gptzfsboot with a 7.1-STABLE > install, but all i got is a : > "No ZFS pools located, can't boot" message. > > I used 7.1-STABLE DVD, but I have copied and installed /boot/pmbr / > boot/gptzfsboot and /boot/loader from a > - -CURRENT system built with your patch and LOADER_ZFS_SUPPORT > > All my disks have valid guid partition tables with p1 of type > freebsd-boot with installed pmbr and gptzfsboot from -CURRENT, > and p2 partition of type freebsd-zfs with a valid pool that i can > mount using LiveFS. > > Any suggestions? > > - -- > Regards, > Nikolay Denev > > I was able to boot from the raidz pool, and now I have working 7.1- STABLE install booting off raidz pool. Sweet! The problem was that I had "export"ed the pool, and gptzfsboot was not able to find it. I had to boot from the LiveFS CD, zpool import it, reboot and everything worked. Now I can only wait for ZFS v13 to hit -STABLE :) Thanks! - -- Regards, Nikolay Denev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (Darwin) iEYEARECAAYFAklrHQcACgkQHNAJ/fLbfrnEnACgrwgaBvMXpd+Iqu0jRSTy6XsS TlsAoJ7rWe+b7iEedphf8wqTOpuRpwfg =J7ZE -----END PGP SIGNATURE----- From bugmaster at FreeBSD.org Mon Jan 12 03:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 12 03:07:53 2009 Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org Message-ID: <200901121106.n0CB6pu6091974@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o bin/130105 fs [zfs] zfs send -R dumps core o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129174 fs [nfs][zfs][panic] NFS v3 Panic when under high load ex o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129084 fs [udf] [panic] udf panic: getblk: size(67584) > MAXBSIZ f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad o 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 o 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 ca o kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D 32 problems total. From helio at loureiro.eng.br Mon Jan 12 09:00:17 2009 From: helio at loureiro.eng.br (Helio Loureiro) Date: Mon Jan 12 09:00:24 2009 Subject: kern/124621: [ext3] [patch] Cannot mount ext2fs partition Message-ID: <200901121700.n0CH0Gs1060137@freefall.freebsd.org> The following reply was made to PR kern/124621; it has been noted by GNATS. From: "Helio Loureiro" To: bug-followup@freebsd.org, paulf@free.fr Cc: Subject: Re: kern/124621: [ext3] [patch] Cannot mount ext2fs partition Date: Mon, 12 Jan 2009 14:34:16 -0200 Hi, I'm facing the same issue. I have an external HD, where I installed Linux Ubuntu a long time ago. I performed recently an upgrade to latest Ubuntu, what reformatted partition da0s1. Old partitions, like da0s2 (home), remain working fine w/ FreeBSD. I checked Inode size paramenter in both: musashi# tune2fs -l /dev/da0s1 | grep -i "inode size" Inode size: 256 musashi# tune2fs -l /dev/da0s2 | grep -i "inode size" Inode size: 128 I'm using the e2fsprogs version you recommended, 1.41.0, in a FreeBSD-7.1: musashi# pkg_glob "*e2fs*" e2fsprogs-1.41.0 musashi# uname -a FreeBSD musashi.br.am.ericsson.se 7.1-RELEASE FreeBSD 7.1-RELEASE #23: Sat Jan 3 23:41:26 BRST 2009 root@musashi.br.am.ericsson.se:/usr/obj/usr/src/sys/MUSASHI i386 So programs like fsck.ext3 are working fine, finding and checking filesyste= ms: e2fsck 1.41.0 (10-Jul-2008) /dev/da0s1: clean, 130703/305824 files, 796572/1220932 blocks musashi# /usr/local/sbin/fsck.ext3 /dev/da0s2 e2fsck 1.41.0 (10-Jul-2008) /dev/da0s2: clean, 219500/12222464 files, 21270465/24414783 blocks So da0s1 isn't accessible while da0s2 is: musashi# mkdir /mnt/da0s{1,2} musashi# mount_ext2fs /dev/da0s1 /mnt/da0s1 musashi# mount_ext2fs /dev/da0s2 /mnt/da0s2 musashi# ls /mnt/da0s1 ls: /mnt/da0s1: Bad file descriptor musashi# ls /mnt/da0s2 backup fotos helio lost+found tmp x I even tried to unload/load ext2fs.ko module, but I didn't see any progress on that. So I believe the issue is reproducible and remains despite the new e2fsprogs release. I'll try the suggested patch and see if it works. --=20 []=B4s Helio Loureiro From ndenev at gmail.com Tue Jan 13 07:47:59 2009 From: ndenev at gmail.com (Nikolay Denev) Date: Tue Jan 13 07:48:06 2009 Subject: Booting from ZFS raidz In-Reply-To: References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <2F0DF92C-4240-48D4-9A5F-8B826D6D6E95@rabson.org> <87E89284-D3BF-4A5A-B6F7-C30709A3F2D9@lassitu.de> <4AC3BEB2-B47E-4280-85E1-C72891412D09@rabson.org> <494F6C21.2000801@tzim.net> <459358DB-15A6-4E27-A99E-D76A2A7DC73F@rabson.org> <12C6C9A1-D4F0-442A-A92C-1B4565AEEAF8@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12 Jan, 2009, at 12:35 , Nikolay Denev wrote: > > > I was able to boot from the raidz pool, and now I have working 7.1- > STABLE install booting off raidz pool. Sweet! > The problem was that I had "export"ed the pool, and gptzfsboot was > not able to find it. I had to boot from the LiveFS CD, > zpool import it, reboot and everything worked. > > Now I can only wait for ZFS v13 to hit -STABLE :) > > Thanks! > > - -- > Regards, > Nikolay Denev Hi Doug, I have just tested how the loader will handle a device failure, and it failed. Here is some info about my setup : The machine has six hot-plug sata drives configured as passthru on a 3Ware controller. There is gptzfsboot installed on their first guid partition, and the rest is for the ZFS raidz1 pool from which the machine boots successfully. I tested yanking the first drive while the machine was up. A few seconds later the 3ware controller saw that device was disconnected and printed some info about this on the console, immediately after that ZFS reported missing vdev and the pool went to DEGRADED mode. Then I rebooted the machine to see if the loader will correctly boot off the degraded pool and this is what I got on the console : 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: zfs:/boot/kernel/kernel boot: ZFS: unexpected object set type lld Then I booted off the LiveFS CD, imported the pool (with the previously removed disk inserted), it resilvered automaticaly, then I scrubbed it without errors and rebooted again... but the loader continues to emit the same messages. - -- Regards, Nikolay Denev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (Darwin) iEYEARECAAYFAklst6cACgkQHNAJ/fLbfrl9RwCfaB3+ICDoBr0j2xwVAyj4ZPe/ h4QAmwQnXWYje7ppiitdWAP1vLvmT1hg =U1mg -----END PGP SIGNATURE----- From stas at FreeBSD.org Sun Jan 18 09:11:39 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sun Jan 18 09:11:46 2009 Subject: ext2 inode size patch - RE: PR kern/124621 In-Reply-To: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> Message-ID: <20090118201138.eeb5d9ad.stas@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 3 Dec 2008 17:53:43 -0500 "Josh Carroll" mentioned: > > Ok, I describe my concern once more. I do not object against the checking > > of the inode size. But, if inode size is changed, then some data is added > > to the inode, that could (and usually does, otherwise why extend it ?) > > change intrerpetation of the inode. Thus, we need a verification of the > > fact that simply ignoring added fields does not damage filesystem or > > cause user data corruption. Verification != testing. > > Let me take another crack at explaining why I think this patch is not dangerous. > > The inode size is determined by reading the following member: > > __u16 s_inode_size; > > of the ext2_super_block structure. > > I took a look at the Linux 2.6.27.7 kernel source, and indeed they do > something very similar if not the same: > > #define EXT2_INODE_SIZE(s) (EXT2_SB(s)->s_inode_size) > > If you compare to what I did: > > #define EXT2_INODE_SIZE(s) ((s)->u.ext2_sb.s_inode_size) > > This is really the same thing, since EXT2_SB is defined (in the Linux > kernel src as): > > #ifdef __KERNEL__ > #include > static inline struct ext2_sb_info *EXT2_SB(struct super_block *sb) > { > return sb->s_fs_info; > } > > And struct ext2_sb_info has the following member: > > int s_inode_size; > > Essentially, the changes I made simply query the existing information > from the filesystem, which is what the Linux kernel does as well. > > The inode size, blocks per group, etc are all defined at filesystem > creation time by mke2fs and it ensures the sanity of the relationship > between the inodes/blocks/block groups. > > The first diagram here: > > http://sunsite.nus.sg/LDP/LDP/tlk/node95.html > > Makes it clear that as long as the number of inodes per block and the > blocks per group is is sane during fs creation, looking up the inode > size as my patch does is fine, since the creation of the filesystem is > ensures a correct by construction situation. We're simply reading the > size of the inode based on the filesystem. > > I hope this is sufficient to convince some further thought about > committing this. > > For those interested in the relevant Linux kernel source, you can have > a look at line 105 of include/linux/ext2_fs.h from the linux-2.6.27.7 > kernel source. > Hi Josh! I've commited the similar patch today that should be fixing your problem. Can you check this, please? Sorry I've missed this thread in the first place. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzYsoACgkQK/VZk+smlYF3ZwCeOyVUdzrKOdu4Pg3ztAZ0QQaY GGIAnA+oL054T0EAajbfwpYSTDRKVISC =jJFT -----END PGP SIGNATURE----- !DSPAM:497362c8967008581431178! From stas at FreeBSD.org Sun Jan 18 09:20:04 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sun Jan 18 09:20:14 2009 Subject: kern/128173: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem Message-ID: <200901181720.n0IHK4t8001671@freefall.freebsd.org> The following reply was made to PR kern/128173; it has been noted by GNATS. From: Stanislav Sedov To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/128173: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem Date: Sun, 18 Jan 2009 20:19:48 +0300 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Christophe! Can you check, please, if recent current suffers from the same problem? The patch I've committed today should solve this issue. I can give you a patch for 7.1 if you're in position to rebuild the kernel. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzZLQACgkQK/VZk+smlYGs+wCdGTrYT8G0Ptt0ICTJ5mNKcaay xIMAn0gtJN2PYsefXuna+GP6aZIVQBPa =0UUe -----END PGP SIGNATURE----- !DSPAM:497364b1967001989116225! From stas at FreeBSD.org Sun Jan 18 09:25:36 2009 From: stas at FreeBSD.org (stas@FreeBSD.org) Date: Sun Jan 18 09:25:43 2009 Subject: kern/128173: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem Message-ID: <200901181725.n0IHPZwG008603@freefall.freebsd.org> Synopsis: [ext2fs] ls gives "Input/output error" on mounted ext3 filesystem State-Changed-From-To: open->feedback State-Changed-By: stas State-Changed-When: Sun Jan 18 17:25:35 UTC 2009 State-Changed-Why: Ask for submitter test. http://www.freebsd.org/cgi/query-pr.cgi?pr=128173 From stas at FreeBSD.org Sun Jan 18 09:25:56 2009 From: stas at FreeBSD.org (stas@FreeBSD.org) Date: Sun Jan 18 09:26:03 2009 Subject: kern/125536: [ext2fs] ext 2 mounts cleanly but fails on commands like ls Message-ID: <200901181725.n0IHPt3x008725@freefall.freebsd.org> Synopsis: [ext2fs] ext 2 mounts cleanly but fails on commands like ls State-Changed-From-To: open->feedback State-Changed-By: stas State-Changed-When: Sun Jan 18 17:25:54 UTC 2009 State-Changed-Why: Ask for submitter test. http://www.freebsd.org/cgi/query-pr.cgi?pr=125536 From stas at FreeBSD.org Sun Jan 18 09:26:16 2009 From: stas at FreeBSD.org (stas@FreeBSD.org) Date: Sun Jan 18 09:26:22 2009 Subject: kern/124621: [ext3] [patch] Cannot mount ext2fs partition Message-ID: <200901181726.n0IHQFTK008822@freefall.freebsd.org> Synopsis: [ext3] [patch] Cannot mount ext2fs partition State-Changed-From-To: open->feedback State-Changed-By: stas State-Changed-When: Sun Jan 18 17:26:15 UTC 2009 State-Changed-Why: Ask for submitter test. http://www.freebsd.org/cgi/query-pr.cgi?pr=124621 From stas at FreeBSD.org Sun Jan 18 09:30:03 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sun Jan 18 09:30:15 2009 Subject: kern/125536: [ext2fs] ext 2 mounts cleanly but fails on commands like ls Message-ID: <200901181730.n0IHU3H2009012@freefall.freebsd.org> The following reply was made to PR kern/125536; it has been noted by GNATS. From: Stanislav Sedov To: james francis toy iv Cc: bug-followup@FreeBSD.org Subject: Re: kern/125536: [ext2fs] ext 2 mounts cleanly but fails on commands like ls Date: Sun, 18 Jan 2009 20:20:36 +0300 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi James! Can you check, please, if recent current suffers from the same problem? The patch I've committed today should solve this issue. I can give you a patch for 7.1 if you're in position to rebuild the kernel. Thanks! - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzZOQACgkQK/VZk+smlYHZ5gCfbKh8dbOXcrve28rKG1xifcVt +AYAnjIdLn13ZgY5tboJsPAz0YaHqH3s =P4lP -----END PGP SIGNATURE----- !DSPAM:497364e1967001660048968! From stas at FreeBSD.org Sun Jan 18 09:30:06 2009 From: stas at FreeBSD.org (Stanislav Sedov) Date: Sun Jan 18 09:30:16 2009 Subject: kern/124621: [ext3] [patch] Cannot mount ext2fs partition Message-ID: <200901181730.n0IHU5ID009184@freefall.freebsd.org> The following reply was made to PR kern/124621; it has been noted by GNATS. From: Stanislav Sedov To: Paul Floyd Cc: bug-followup@FreeBSD.org Subject: Re: kern/124621: [ext3] [patch] Cannot mount ext2fs partition Date: Sun, 18 Jan 2009 20:23:22 +0300 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Paul! Can you check, please, if recent current suffers from the same problem? The patch I've committed today should solve this issue. I can give you a patch for 7.1 if you're in position to rebuild the kernel. Thanks! - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklzZYoACgkQK/VZk+smlYGE/ACdE+ybZzJxb/5Nb1Qi1CyILVtW 6aAAnieoGkMpBCoFvwKAE1yVWgxu5pbA =Nn7G -----END PGP SIGNATURE----- !DSPAM:49736588967004808450424! From brampton+freebsd-fs at gmail.com Sun Jan 18 17:30:45 2009 From: brampton+freebsd-fs at gmail.com (Andrew Brampton) Date: Sun Jan 18 17:30:52 2009 Subject: Pseudofs and pfs_attr_t for non-process based files Message-ID: Hi, I've recently been coding a pseudofs based file system to export data from a custom kernel module, and allow users to control the module via the file system. Anyway, I quite like how simple it is to use pseudofs, but I found one annoying "feature". If I call pfs_create_{dir, file, link} with a pfs_attr_t function pointer, my function will never be called. I tracked this problem to the function pfs_getattr inside sys/fs/pseudofs/pseudofs_vnops.c. It has the following lines of code: if (proc != NULL) { ... if (pn->pn_attr != NULL) error = pn_attr(curthread, proc, pn, vap); ... } Basically pn_attr calls my pfs_attr_t function pointer, but only if the proc != null. Now in my case none of my files are created PFS_PROCDEP flag, which mean proc will always be null. So unless you are writing a pseudofs which is dependent on the process calling it, you cannot use a pfs_attr_t function pointer, meaning I can't change the attributes on my pseudo files. Now, to fix this problem I made a very simple patch which will call pn_attr regardless of proc being null or not. By doing this I had to also make a minor change in procfs.c as it assumes a valid proc is always passed in. I'd be grateful if someone look over my patches, and advise me if this was the correct thing to do. Also I'd be interested to know why this was original coded like this? Or was it just a oversight? Just for reference there is also a few more callbacks for various file system operations, with all of them working if proc is null, with one exception, the pfs_vis_t callback. Perhaps that should also be updated also? Thanks Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: pseudofs_vnops.patch Type: application/octet-stream Size: 826 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090119/799808d4/pseudofs_vnops.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: procfs.patch Type: application/octet-stream Size: 1051 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090119/799808d4/procfs.obj From bugmaster at FreeBSD.org Mon Jan 19 03:06:58 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 19 03:07:46 2009 Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org Message-ID: <200901191106.n0JB6v5c062948@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o bin/130105 fs [zfs] zfs send -R dumps core o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129174 fs [nfs] [zfs] [panic] NFS v3 Panic when under high load o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129084 fs [udf] [panic] udf panic: getblk: size(67584) > MAXBSIZ f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D 32 problems total. From jw.hendy at gmail.com Tue Jan 20 08:29:46 2009 From: jw.hendy at gmail.com (John Hendy) Date: Tue Jan 20 08:30:22 2009 Subject: OS X/FreeBSD shared zfs partition Message-ID: Hi, I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to share a partition for storage between the two. I looked into getting HFS+ to work on FreeBSD (http://forums.freebsd.org/showthread.php?t=1198) but did not succeed. Then I ran across these two pages: - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html - http://zfs.macosforge.org/trac/wiki I used them to successfully change my Users folder in OS X to a zfs filesystem on a partition separate from my main OS X system/boot files. Now I just want to mount that partition from FreeBSD. Is this possible? I can see the slice in /dev as ad5s3, but there's no partitions on that slice to mount (ad5s3a, for example), nor am I familiar enough with ZFS to know what it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 /media/temp' without success. zfs.ko is loaded (seen in kldstat) and gives the usual message of it being experimental and being version 6.0. In a post on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was suggested that I try 'zpool list' but that returned 'no pools available'. I tried 'zfs list' as well and got 'no datasets available'. My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on the GPT and type B4 iirc on the MBR). I used an EFI booting program called rEFIt to sync the tables - could the MBR type of the slice be the reason I can't mount it from FreeBSD? I've searched long and hard for any posts about using zfs as a way to share a partition between any two OSs, but have not found any references on how to use a zfs slice as a shared data partition. Can it only be mounted from the OS in which it was created? Any thoughts on what I might do here? Thanks much, John From boris.kotzev at gmail.com Tue Jan 20 11:29:27 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Tue Jan 20 11:29:33 2009 Subject: OS X/FreeBSD shared zfs partition Message-ID: <200901202058.25355.boris.kotzev@gmail.com> > Hi, > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to share a > partition for storage between the two. I looked into getting HFS+ to work on > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198) > but > did not succeed. Then I ran across these two pages: > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > - http://zfs.macosforge.org/trac/wiki > > I used them to successfully change my Users folder in OS X to a zfs > filesystem on a partition separate from my main OS X system/boot files. Now > I just want to mount that partition from FreeBSD. Is this possible? I can > see the slice in /dev as ad5s3, but there's no partitions on that slice to > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know what > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and gives > the usual message of it being experimental and being version 6.0. In a post > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > suggested that I try 'zpool list' but that returned 'no pools available'. I > tried 'zfs list' as well and got 'no datasets available'. > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on the > GPT and type B4 iirc on the MBR). I used an EFI booting program called rEFIt > to sync the tables - could the MBR type of the slice be the reason I can't > mount it from FreeBSD? > > I've searched long and hard for any posts about using zfs as a way to share > a partition between any two OSs, but have not found any references on how to > use a zfs slice as a shared data partition. Can it only be mounted from the > OS in which it was created? Any thoughts on what I might do here? > > > Thanks much, > John What does zfs import return? Regards, Boris Kotzev From boris.kotzev at gmail.com Tue Jan 20 11:33:09 2009 From: boris.kotzev at gmail.com (Boris Kotzev) Date: Tue Jan 20 11:33:16 2009 Subject: OS X/FreeBSD shared zfs partition Message-ID: <200901202101.27544.boris.kotzev@gmail.com> > Hi, > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to share a > partition for storage between the two. I looked into getting HFS+ to work on > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198) > but > did not succeed. Then I ran across these two pages: > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > - http://zfs.macosforge.org/trac/wiki > > I used them to successfully change my Users folder in OS X to a zfs > filesystem on a partition separate from my main OS X system/boot files. Now > I just want to mount that partition from FreeBSD. Is this possible? I can > see the slice in /dev as ad5s3, but there's no partitions on that slice to > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know what > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and gives > the usual message of it being experimental and being version 6.0. In a post > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > suggested that I try 'zpool list' but that returned 'no pools available'. I > tried 'zfs list' as well and got 'no datasets available'. > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on the > GPT and type B4 iirc on the MBR). I used an EFI booting program called rEFIt > to sync the tables - could the MBR type of the slice be the reason I can't > mount it from FreeBSD? > > I've searched long and hard for any posts about using zfs as a way to share > a partition between any two OSs, but have not found any references on how to > use a zfs slice as a shared data partition. Can it only be mounted from the > OS in which it was created? Any thoughts on what I might do here? > > > Thanks much, > John I am sorry, I wanted to ask what zpool import returns. Regards, Boris Kotzev From jw.hendy at gmail.com Tue Jan 20 16:08:15 2009 From: jw.hendy at gmail.com (John Hendy) Date: Tue Jan 20 16:08:20 2009 Subject: OS X/FreeBSD shared zfs partition In-Reply-To: <200901202101.27544.boris.kotzev@gmail.com> References: <200901202101.27544.boris.kotzev@gmail.com> Message-ID: Wow... I really didn't expect that to work! Well, it 'kind of worked'. Here's what I got: I did 'zpool import' and got the usual 'ZFS is experimental in FreeBSD, ZFS filesystem version 6' and it said something like 'you can import pools by name' (sorry - i missed the exact message). Then I did 'zfs lilst' and tank was listed, but not tank/jwhendy. Then I did 'zfs mount tank/jwhendy' and got: 'Mismatched versions: Filesystem is version 2 on-disk format, which is incompatible with this software version 1! You can force mounting with -f' I did 'zfs mount -f tank/jwhendy' and it said 'Cannot mount 'tank/jwhendy': Operation not supported', but zfs list shows: NAME USED AVAIL REFER MOUNTPOINT tank 11.4G 27.2G 390K /tank tank/jwhendy 11.4G 27.2G 11.4G /tank/jwhendy So... it appears it mounted? when I cd /tank/jwhendy, though, all that is in the folder is a file called .autodiskmounted, which I assume is used by OS X. I think we've made some progress... any way to go the whole way? Can I upgrade the zfs version in FreeBSD since it complains about the mismatched software versions? Just a thought. Thanks! John On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev wrote: > > Hi, > > > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to > share a > > partition for storage between the two. I looked into getting HFS+ to work > on > > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< > http://forums.freebsd.org/showthread.php?t=1198> > > but > > did not succeed. Then I ran across these two pages: > > > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > > - http://zfs.macosforge.org/trac/wiki > > > > I used them to successfully change my Users folder in OS X to a zfs > > filesystem on a partition separate from my main OS X system/boot files. > Now > > I just want to mount that partition from FreeBSD. Is this possible? I can > > see the slice in /dev as ad5s3, but there's no partitions on that slice > to > > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know > what > > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and > gives > > the usual message of it being experimental and being version 6.0. In a > post > > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > > suggested that I try 'zpool list' but that returned 'no pools available'. > I > > tried 'zfs list' as well and got 'no datasets available'. > > > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on > the > > GPT and type B4 iirc on the MBR). I used an EFI booting program called > rEFIt > > to sync the tables - could the MBR type of the slice be the reason I > can't > > mount it from FreeBSD? > > > > I've searched long and hard for any posts about using zfs as a way to > share > > a partition between any two OSs, but have not found any references on how > to > > use a zfs slice as a shared data partition. Can it only be mounted from > the > > OS in which it was created? Any thoughts on what I might do here? > > > > > > Thanks much, > > John > > I am sorry, I wanted to ask what > > zpool import > > returns. > > Regards, > > Boris Kotzev > > > > > > > From jw.hendy at gmail.com Tue Jan 20 16:12:59 2009 From: jw.hendy at gmail.com (John Hendy) Date: Tue Jan 20 16:13:05 2009 Subject: OS X/FreeBSD shared zfs partition In-Reply-To: <200901202101.27544.boris.kotzev@gmail.com> References: <200901202101.27544.boris.kotzev@gmail.com> Message-ID: Oh, and 'zpool status' returns: pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ad5s3 ONLINE 0 0 0 And when I just tried 'zfs unmount tank/jwhendy' I get 'cannot unmount tank/jwhendy: not currently mounted'. Just wanted to add that... I thought tank/jwhendy hendy was mounted since it's mountpoint directory was not empty, but according to zfs it was not mounted. Thanks, John On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev wrote: > > Hi, > > > > I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to > share a > > partition for storage between the two. I looked into getting HFS+ to work > on > > FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< > http://forums.freebsd.org/showthread.php?t=1198> > > but > > did not succeed. Then I ran across these two pages: > > > > - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html > > - http://zfs.macosforge.org/trac/wiki > > > > I used them to successfully change my Users folder in OS X to a zfs > > filesystem on a partition separate from my main OS X system/boot files. > Now > > I just want to mount that partition from FreeBSD. Is this possible? I can > > see the slice in /dev as ad5s3, but there's no partitions on that slice > to > > mount (ad5s3a, for example), nor am I familiar enough with ZFS to know > what > > it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 > > /media/temp' without success. zfs.ko is loaded (seen in kldstat) and > gives > > the usual message of it being experimental and being version 6.0. In a > post > > on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was > > suggested that I try 'zpool list' but that returned 'no pools available'. > I > > tried 'zfs list' as well and got 'no datasets available'. > > > > My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both > > show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on > the > > GPT and type B4 iirc on the MBR). I used an EFI booting program called > rEFIt > > to sync the tables - could the MBR type of the slice be the reason I > can't > > mount it from FreeBSD? > > > > I've searched long and hard for any posts about using zfs as a way to > share > > a partition between any two OSs, but have not found any references on how > to > > use a zfs slice as a shared data partition. Can it only be mounted from > the > > OS in which it was created? Any thoughts on what I might do here? > > > > > > Thanks much, > > John > > I am sorry, I wanted to ask what > > zpool import > > returns. > > Regards, > > Boris Kotzev > > > > > > > From morganw at chemikals.org Tue Jan 20 18:41:08 2009 From: morganw at chemikals.org (Wes Morgan) Date: Tue Jan 20 18:41:15 2009 Subject: OS X/FreeBSD shared zfs partition In-Reply-To: References: <200901202101.27544.boris.kotzev@gmail.com> Message-ID: On Tue, 20 Jan 2009, John Hendy wrote: > Wow... I really didn't expect that to work! Well, it 'kind of worked'. > Here's what I got: > > I did 'zpool import' and got the usual 'ZFS is experimental in FreeBSD, ZFS > filesystem version 6' and it said something like 'you can import pools by > name' (sorry - i missed the exact message). Then I did 'zfs lilst' and tank > was listed, but not tank/jwhendy. That version "6" is the pool format. The actual filesystem on-disk versions are different. In -current, the pool version is 13 and filesystem version is 3, according to both "zpool upgrade" and "zfs upgrade". Sounds like the zfs code in OS X is more recent than that in -stable. > Then I did 'zfs mount tank/jwhendy' and got: > > 'Mismatched versions: Filesystem is version 2 on-disk format, which is > incompatible with this software version 1! You can force mounting with -f' > > I did 'zfs mount -f tank/jwhendy' and it said 'Cannot mount 'tank/jwhendy': > Operation not supported', but zfs list shows: Yeah I wouldn't advice doing that, no telling what will happen. zfs list will show you filesystem status regardless of mount status, it's just reading the pool data I imagine. > > NAME USED AVAIL REFER MOUNTPOINT > tank 11.4G 27.2G 390K /tank > tank/jwhendy 11.4G 27.2G 11.4G /tank/jwhendy > > So... it appears it mounted? when I cd /tank/jwhendy, though, all that is in > the folder is a file called .autodiskmounted, which I assume is used by OS > X. > > I think we've made some progress... any way to go the whole way? Can I > upgrade the zfs version in FreeBSD since it complains about the mismatched > software versions? Just a thought. > > > > Thanks! > John > > On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev wrote: > >>> Hi, >>> >>> I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to >> share a >>> partition for storage between the two. I looked into getting HFS+ to work >> on >>> FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< >> http://forums.freebsd.org/showthread.php?t=1198> >>> but >>> did not succeed. Then I ran across these two pages: >>> >>> - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html >>> - http://zfs.macosforge.org/trac/wiki >>> >>> I used them to successfully change my Users folder in OS X to a zfs >>> filesystem on a partition separate from my main OS X system/boot files. >> Now >>> I just want to mount that partition from FreeBSD. Is this possible? I can >>> see the slice in /dev as ad5s3, but there's no partitions on that slice >> to >>> mount (ad5s3a, for example), nor am I familiar enough with ZFS to know >> what >>> it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 >>> /media/temp' without success. zfs.ko is loaded (seen in kldstat) and >> gives >>> the usual message of it being experimental and being version 6.0. In a >> post >>> on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was >>> suggested that I try 'zpool list' but that returned 'no pools available'. >> I >>> tried 'zfs list' as well and got 'no datasets available'. >>> >>> My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they both >>> show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on >> the >>> GPT and type B4 iirc on the MBR). I used an EFI booting program called >> rEFIt >>> to sync the tables - could the MBR type of the slice be the reason I >> can't >>> mount it from FreeBSD? >>> >>> I've searched long and hard for any posts about using zfs as a way to >> share >>> a partition between any two OSs, but have not found any references on how >> to >>> use a zfs slice as a shared data partition. Can it only be mounted from >> the >>> OS in which it was created? Any thoughts on what I might do here? >>> >>> >>> Thanks much, >>> John >> >> I am sorry, I wanted to ask what >> >> zpool import >> >> returns. >> >> Regards, >> >> Boris Kotzev From jw.hendy at gmail.com Tue Jan 20 20:29:46 2009 From: jw.hendy at gmail.com (John Hendy) Date: Tue Jan 20 20:29:53 2009 Subject: OS X/FreeBSD shared zfs partition In-Reply-To: References: <200901202101.27544.boris.kotzev@gmail.com> Message-ID: Thanks Boris and Jake. Is this 7.0 current we're talking about, or 8.0? I'm still pretty new to FreeBSD and trying to sort the nomenclature: release, current, stable... along with each of those I believe is also a version (7.0, 7.1, 8.0, etc.). Just looking to know what I should run to have a compatible version of the filesystem. I do not want bleeding edge, so 8.0 is out... I wouldn't mind something like 7.1 stable, though. Would that be possible? Thanks, John On Tue, Jan 20, 2009 at 6:19 PM, Jake Scott wrote: > MacOS has a later version of the file system. If you don't have any data > you care about on it yet, then try re-creating the pool in FreeBSD and then > importing it into MacOS. Otherwise, you will need FreeBSD current... > > > J> > > > > > On Tue, 20 Jan 2009, John Hendy wrote: > > Oh, and 'zpool status' returns: >> >> pool: tank >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> tank ONLINE 0 0 0 >> ad5s3 ONLINE 0 0 0 >> >> And when I just tried 'zfs unmount tank/jwhendy' I get 'cannot unmount >> tank/jwhendy: not currently mounted'. Just wanted to add that... I thought >> tank/jwhendy hendy was mounted since it's mountpoint directory was not >> empty, but according to zfs it was not mounted. >> >> >> Thanks, >> John >> >> On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev > >wrote: >> >> Hi, >>>> >>>> I dual boot OS X and FreeBSD (currently 7.0-i386) and have wanted to >>>> >>> share a >>> >>>> partition for storage between the two. I looked into getting HFS+ to >>>> work >>>> >>> on >>> >>>> FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< >>>> >>> http://forums.freebsd.org/showthread.php?t=1198> >>> >>>> but >>>> did not succeed. Then I ran across these two pages: >>>> >>>> - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html >>>> - http://zfs.macosforge.org/trac/wiki >>>> >>>> I used them to successfully change my Users folder in OS X to a zfs >>>> filesystem on a partition separate from my main OS X system/boot files. >>>> >>> Now >>> >>>> I just want to mount that partition from FreeBSD. Is this possible? I >>>> can >>>> see the slice in /dev as ad5s3, but there's no partitions on that slice >>>> >>> to >>> >>>> mount (ad5s3a, for example), nor am I familiar enough with ZFS to know >>>> >>> what >>> >>>> it should look like from FreeBSD. I have tried 'mount -t zfs /dev/ad5s3 >>>> /media/temp' without success. zfs.ko is loaded (seen in kldstat) and >>>> >>> gives >>> >>>> the usual message of it being experimental and being version 6.0. In a >>>> >>> post >>> >>>> on the forums (http://forums.freebsd.org/showthread.php?t=1613) it was >>>> suggested that I try 'zpool list' but that returned 'no pools >>>> available'. >>>> >>> I >>> >>>> tried 'zfs list' as well and got 'no datasets available'. >>>> >>>> My GUID partition table (OS X) and MBR (FreeBSD) are synced, so they >>>> both >>>> show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris Usr' on >>>> >>> the >>> >>>> GPT and type B4 iirc on the MBR). I used an EFI booting program called >>>> >>> rEFIt >>> >>>> to sync the tables - could the MBR type of the slice be the reason I >>>> >>> can't >>> >>>> mount it from FreeBSD? >>>> >>>> I've searched long and hard for any posts about using zfs as a way to >>>> >>> share >>> >>>> a partition between any two OSs, but have not found any references on >>>> how >>>> >>> to >>> >>>> use a zfs slice as a shared data partition. Can it only be mounted from >>>> >>> the >>> >>>> OS in which it was created? Any thoughts on what I might do here? >>>> >>>> >>>> Thanks much, >>>> John >>>> >>> >>> I am sorry, I wanted to ask what >>> >>> zpool import >>> >>> returns. >>> >>> Regards, >>> >>> Boris Kotzev >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> >> From chris at young-alumni.com Tue Jan 20 21:04:25 2009 From: chris at young-alumni.com (Chris Ruiz) Date: Tue Jan 20 21:04:32 2009 Subject: OS X/FreeBSD shared zfs partition In-Reply-To: References: <200901202101.27544.boris.kotzev@gmail.com> Message-ID: <818F3AAA-919C-4848-826C-4982592649FF@young-alumni.com> On Jan 20, 2009, at 10:29 PM, John Hendy wrote: > Thanks Boris and Jake. > > Is this 7.0 current we're talking about, or 8.0? I'm still pretty > new to > FreeBSD and trying to sort the nomenclature: release, current, > stable... > along with each of those I believe is also a version (7.0, 7.1, 8.0, > etc.). > Just looking to know what I should run to have a compatible version > of the > filesystem. I do not want bleeding edge, so 8.0 is out... I wouldn't > mind > something like 7.1 stable, though. Would that be possible? 7 = STABLE, 8 = CURRENT. I have successfully used a zfs flash drive on osx 10.5.6 w/ zfs 119 and freebsd 7.1. Try setting up your zpool with osx's implementation. When you switch between operating systems, you will need to zpool import -f. Also, osx uses acls to prevent you from being able to execute anything written to your zfs filesystems from any other operating system (this shouldn't matter if you are just storing data). You shouldn't need to use mount at all, your filesystems will be auto-mounted when you import your zpool. Hope this helps, Chris Ruiz > > Thanks, > John > > On Tue, Jan 20, 2009 at 6:19 PM, Jake Scott wrote: > >> MacOS has a later version of the file system. If you don't have >> any data >> you care about on it yet, then try re-creating the pool in FreeBSD >> and then >> importing it into MacOS. Otherwise, you will need FreeBSD current... >> >> >> J> >> >> >> >> >> On Tue, 20 Jan 2009, John Hendy wrote: >> >> Oh, and 'zpool status' returns: >>> >>> pool: tank >>> state: ONLINE >>> scrub: none requested >>> config: >>> >>> NAME STATE READ WRITE CKSUM >>> tank ONLINE 0 0 0 >>> ad5s3 ONLINE 0 0 0 >>> >>> And when I just tried 'zfs unmount tank/jwhendy' I get 'cannot >>> unmount >>> tank/jwhendy: not currently mounted'. Just wanted to add that... I >>> thought >>> tank/jwhendy hendy was mounted since it's mountpoint directory was >>> not >>> empty, but according to zfs it was not mounted. >>> >>> >>> Thanks, >>> John >>> >>> On Tue, Jan 20, 2009 at 1:01 PM, Boris Kotzev >>> >>> wrote: >>> >>> Hi, >>>>> >>>>> I dual boot OS X and FreeBSD (currently 7.0-i386) and have >>>>> wanted to >>>>> >>>> share a >>>> >>>>> partition for storage between the two. I looked into getting HFS >>>>> + to >>>>> work >>>>> >>>> on >>>> >>>>> FreeBSD (http://forums.freebsd.org/showthread.php?t=1198)< >>>>> >>>> http://forums.freebsd.org/showthread.php?t=1198> >>>> >>>>> but >>>>> did not succeed. Then I ran across these two pages: >>>>> >>>>> - http://blog.igorminar.com/2009/01/using-zfs-with-mac-os-x-105.html >>>>> - http://zfs.macosforge.org/trac/wiki >>>>> >>>>> I used them to successfully change my Users folder in OS X to a >>>>> zfs >>>>> filesystem on a partition separate from my main OS X system/boot >>>>> files. >>>>> >>>> Now >>>> >>>>> I just want to mount that partition from FreeBSD. Is this >>>>> possible? I >>>>> can >>>>> see the slice in /dev as ad5s3, but there's no partitions on >>>>> that slice >>>>> >>>> to >>>> >>>>> mount (ad5s3a, for example), nor am I familiar enough with ZFS >>>>> to know >>>>> >>>> what >>>> >>>>> it should look like from FreeBSD. I have tried 'mount -t zfs / >>>>> dev/ad5s3 >>>>> /media/temp' without success. zfs.ko is loaded (seen in kldstat) >>>>> and >>>>> >>>> gives >>>> >>>>> the usual message of it being experimental and being version >>>>> 6.0. In a >>>>> >>>> post >>>> >>>>> on the forums (http://forums.freebsd.org/showthread.php?t=1613) >>>>> it was >>>>> suggested that I try 'zpool list' but that returned 'no pools >>>>> available'. >>>>> >>>> I >>>> >>>>> tried 'zfs list' as well and got 'no datasets available'. >>>>> >>>>> My GUID partition table (OS X) and MBR (FreeBSD) are synced, so >>>>> they >>>>> both >>>>> show disk0s3 (OS X)/partition 3 as type Solaris (It's 'Solaris >>>>> Usr' on >>>>> >>>> the >>>> >>>>> GPT and type B4 iirc on the MBR). I used an EFI booting program >>>>> called >>>>> >>>> rEFIt >>>> >>>>> to sync the tables - could the MBR type of the slice be the >>>>> reason I >>>>> >>>> can't >>>> >>>>> mount it from FreeBSD? >>>>> >>>>> I've searched long and hard for any posts about using zfs as a >>>>> way to >>>>> >>>> share >>>> >>>>> a partition between any two OSs, but have not found any >>>>> references on >>>>> how >>>>> >>>> to >>>> >>>>> use a zfs slice as a shared data partition. Can it only be >>>>> mounted from >>>>> >>>> the >>>> >>>>> OS in which it was created? Any thoughts on what I might do here? >>>>> >>>>> >>>>> Thanks much, >>>>> John >>>>> >>>> >>>> I am sorry, I wanted to ask what >>>> >>>> zpool import >>>> >>>> returns. >>>> >>>> Regards, >>>> >>>> Boris Kotzev >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>> freebsd-fs@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>> To unsubscribe, send any mail to "freebsd-fs- >>> unsubscribe@freebsd.org" >>> >>> > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From fbsd at dannysplace.net Tue Jan 20 22:40:34 2009 From: fbsd at dannysplace.net (Danny Carroll) Date: Tue Jan 20 22:40:40 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: References: <20081031033208.GA21220@icarus.home.lan> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> Message-ID: <4976C370.4030406@dannysplace.net> Koen Smits wrote: > Please let us know what Areca says about the caching. > If you ask me, these results definitely are cached. > Sorry for the delay. Areca got back to me. It took a few days but I got someone who seemed to know what they were talking about. >From what I can gather the cache is always on. You can configure it to be writeback or writethrough in some situations but when that is not an option, writethrough is the default. I could not get any information about read caching although I might send an email to see what happens. Here is the transcript of the conversation: Me: I have a rather simple question about the 1231 controller. Can you please explain the difference between using disks in JBOD mode and using disks in passthrough mode. I have a feeling that the controller uses it's onboard cache when in passthrough mode. Is this the case? Also, are both read and write operations cached? Areca Support: Dear Sir, the only difference is in JBOD mode, controller configure all drives as passthrough disk. in RAID mode, you have to configure passthrough disk by yourself in RAID mode in other words, you can use raid with passthrough disks at saem time in RAID mode but JBOD mode not. Me: So does that mean if I use passthrough, I am not protected by the cache/battery backup? I ask because there is an option for cache mode when creating a passthrough disk. i.e. Write-Back or Write-Through Areca Support: Dear Sir, in JBOD mode, the default setting writeback mode. with writeback mode, you will need a battery module to protect the data remain in cache in case you got a power failure problem. Me: And so in Passthrough mode I am still protected with the battery backup? So JBOD = WriteBack Cache with protection of the battery backup. Passthrough = WriteBack or WriteThrough also with protection of the battery backup. Is this correct? Areca Support: Dear Sir, if you have battery module attached, yes. From kgysmits at gmail.com Wed Jan 21 01:16:09 2009 From: kgysmits at gmail.com (Koen Smits) Date: Wed Jan 21 01:16:22 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: <4976C370.4030406@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> <4976C370.4030406@dannysplace.net> Message-ID: > > Areca Support: > Dear Sir, > the only difference is > in JBOD mode, controller configure all drives as passthrough disk. > in RAID mode, you have to configure passthrough disk by yourself in RAID > mode > > in other words, you can use raid with passthrough disks at saem time in > RAID mode but JBOD mode not. > > Me: > So does that mean if I use passthrough, I am not protected by the > cache/battery backup? I ask because there is an option for cache mode > when creating a passthrough disk. i.e. Write-Back or Write-Through missed my 'reply to all' button, here goes the 2nd try. So 'passthrough' means that the controller lets the OS see the physical disks just as they are, but with an invisible cache in between that buffers operations. This way there is no advantage of the onboard XOR engine, but you do profit from the intelligent cache, which is the most important anyway imho. JBOD mode is at a disadvantage because in this mode the OS sees one large drive, and is not able to stripe the data to multiple disks, not taking advantage of the fact that you have multple spindles available. Makes sense to me :). I must admit, I do like these results. Very promising. Further tests would be using an SSD for the ZIL, testing linux and NT, etc. But let's not go there ;). From fbsd at dannysplace.net Wed Jan 21 05:15:20 2009 From: fbsd at dannysplace.net (Danny Carroll) Date: Wed Jan 21 05:15:27 2009 Subject: Areca vs. ZFS performance testing. In-Reply-To: References: <20081031033208.GA21220@icarus.home.lan> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> <4976C370.4030406@dannysplace.net> Message-ID: <49771FEE.1070606@dannysplace.net> Koen Smits wrote: > Areca Support: > Dear Sir, > the only difference is > in JBOD mode, controller configure all drives as passthrough disk. > in RAID mode, you have to configure passthrough disk by yourself in RAID > mode > > in other words, you can use raid with passthrough disks at saem time in > RAID mode but JBOD mode not. > > Me: > So does that mean if I use passthrough, I am not protected by the > cache/battery backup? I ask because there is an option for cache mode > when creating a passthrough disk. i.e. Write-Back or Write-Through > > > So 'passthrough' means that the controller lets the OS see the physical > disks just as they are, but with an invisible cache in between that > buffers operations. This way there is no advantage of the onboard XOR > engine, but you do profit from the intelligent cache, which is the most > important anyway imho. Not exactly. In JBOD mode ALL disks are passed through to the OS. You cannot have RAID. The cache is set to Write-Back. In RAID mode, you can mix raid5, raid6 and Passthrough (which are like JBOD but allow writethrough or writeback cache at your discretion). > JBOD mode is at a disadvantage because in this mode the OS sees one > large drive, and is not able to stripe the data to multiple disks, not > taking advantage of the fact that you have multple spindles available. > Makes sense to me :). No, in JBOD, the OS sees all disks individually. What you are talking about is a concatenated disk set which I don't think has a raid level. > I must admit, I do like these results. Very promising. Me too, although I am not sure if I like the idea of turning off the cache flushes in ZFS. I'd be a lot happier if the Areca card would tell me how 'full' the cache was. I'd also love to know if there was a way for the disk to tell me what the status if it's own cache is. > Further tests would be using an SSD for the ZIL, testing linux and NT, > etc. But let's not go there ;). Nope :-) -D From des at des.no Wed Jan 21 08:25:47 2009 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Wed Jan 21 08:25:54 2009 Subject: Pseudofs and pfs_attr_t for non-process based files In-Reply-To: (Andrew Brampton's message of "Mon, 19 Jan 2009 01:01:36 +0000") References: Message-ID: <868wp4pqwm.fsf@ds4.des.no> "Andrew Brampton" writes: > Basically pn_attr calls my pfs_attr_t function pointer, but only if > the proc != null. Now in my case none of my files are created > PFS_PROCDEP flag, which mean proc will always be null. So unless you > are writing a pseudofs which is dependent on the process calling it, > you cannot use a pfs_attr_t function pointer, meaning I can't change > the attributes on my pseudo files. > > Now, to fix this problem I made a very simple patch which will call > pn_attr regardless of proc being null or not. By doing this I had to > also make a minor change in procfs.c as it assumes a valid proc is > always passed in. Sounds sensible, but your patches are mangled. Could you please regenerate them using 'svn diff -x-p' on a non-Windows machine? DES -- Dag-Erling Sm?rgrav - des@des.no From brampton+freebsd-fs at gmail.com Wed Jan 21 09:37:45 2009 From: brampton+freebsd-fs at gmail.com (Andrew Brampton) Date: Wed Jan 21 09:37:51 2009 Subject: Pseudofs and pfs_attr_t for non-process based files In-Reply-To: <868wp4pqwm.fsf@ds4.des.no> References: <868wp4pqwm.fsf@ds4.des.no> Message-ID: 2009/1/21 Dag-Erling Sm?rgrav : > Sounds sensible, but your patches are mangled. Could you please > regenerate them using 'svn diff -x-p' on a non-Windows machine? When you say mangled, did you just mean they had windows new lines? Regardless I've reattached the patches (with unix new lines), and using the -x-p command. I wasn't aware of -x-p but it looks useful. Enjoy Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: pseudofs_vnops.patch Type: application/octet-stream Size: 680 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090121/affb8664/pseudofs_vnops.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: procfs.patch Type: application/octet-stream Size: 916 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090121/affb8664/procfs.obj From des at des.no Thu Jan 22 07:21:12 2009 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Thu Jan 22 07:21:20 2009 Subject: Pseudofs and pfs_attr_t for non-process based files In-Reply-To: (Andrew Brampton's message of "Wed, 21 Jan 2009 17:37:43 +0000") References: <868wp4pqwm.fsf@ds4.des.no> Message-ID: <86iqo74ba1.fsf@ds4.des.no> Andrew Brampton writes: > Dag-Erling Sm?rgrav writes: > > Sounds sensible, but your patches are mangled. Could you please > > regenerate them using 'svn diff -x-p' on a non-Windows machine? > When you say mangled, did you just mean they had windows new lines? That, and incorrect indentation, which your new patches fixed. A tip: if your MUA allows it, set the MIME-type for patches to text/x-patch (or, as last resort, text/plain), otherwise they may get stripped by mailing list software and some corporate / institutional email gateways. In procfs_attr(), the vap->va_[ug]id assignments are redundant, since at this point pfs_getattr() has already done the exact same thing. The rest of the patch is fine, modulo style issues which already existed in my code. DES -- Dag-Erling Sm?rgrav - des@des.no From brampton+freebsd-fs at gmail.com Fri Jan 23 06:05:57 2009 From: brampton+freebsd-fs at gmail.com (Andrew Brampton) Date: Fri Jan 23 06:06:03 2009 Subject: Pseudofs and pfs_attr_t for non-process based files In-Reply-To: <86iqo74ba1.fsf@ds4.des.no> References: <868wp4pqwm.fsf@ds4.des.no> <86iqo74ba1.fsf@ds4.des.no> Message-ID: 2009/1/22 Dag-Erling Sm?rgrav : > In procfs_attr(), the vap->va_[ug]id assignments are redundant, since at > this point pfs_getattr() has already done the exact same thing. The > rest of the patch is fine, modulo style issues which already existed in > my code. Here are both patches again, but only the procfs patch has changed. I have now removed the redundant code. thanks Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: pseudofs_vnops.patch Type: text/x-patch Size: 680 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090123/3dce0279/pseudofs_vnops.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: procfs.patch Type: text/x-patch Size: 838 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090123/3dce0279/procfs.bin From linimon at FreeBSD.org Sun Jan 25 12:36:04 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Jan 25 12:36:16 2009 Subject: kern/130979: [smbfs] [panic] boot/kernel/smbfs.ko Message-ID: <200901252036.n0PKa4WW033125@freefall.freebsd.org> Old Synopsis: [panic] boot/kernel/smbfs.ko New Synopsis: [smbfs] [panic] boot/kernel/smbfs.ko Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 25 20:35:41 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=130979 From linimon at FreeBSD.org Sun Jan 25 17:18:14 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Jan 25 17:18:26 2009 Subject: kern/130920: [msdosfs] cp(1) takes 100% CPU time while copying file from harddisk to pendrive Message-ID: <200901260118.n0Q1IDPc041753@freefall.freebsd.org> Synopsis: [msdosfs] cp(1) takes 100% CPU time while copying file from harddisk to pendrive Responsible-Changed-From-To: freebsd-i386->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jan 26 01:18:03 UTC 2009 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=130920 From bugmaster at FreeBSD.org Mon Jan 26 03:06:56 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 26 03:07:45 2009 Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org Message-ID: <200901261106.n0QB6suh024243@freefall.freebsd.org> 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/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o bin/130105 fs [zfs] zfs send -R dumps core o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129174 fs [nfs] [zfs] [panic] NFS v3 Panic when under high load o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129084 fs [udf] [panic] udf panic: getblk: size(67584) > MAXBSIZ f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D 34 problems total. From linimon at FreeBSD.org Mon Jan 26 18:53:21 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Jan 26 18:53:32 2009 Subject: kern/131024: [ext3fs] Writing to ext3 partition causes endless loop Message-ID: <200901270253.n0R2rKpm042435@freefall.freebsd.org> Old Synopsis: Writing to ext3 partition causes endless loop New Synopsis: [ext3fs] Writing to ext3 partition causes endless loop Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Jan 27 02:52:59 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131024 From kib at FreeBSD.org Tue Jan 27 01:52:37 2009 From: kib at FreeBSD.org (kib@FreeBSD.org) Date: Tue Jan 27 01:52:43 2009 Subject: kern/131024: [ext3fs] Writing to ext3 partition causes endless loop Message-ID: <200901270952.n0R9qaj8097306@freefall.freebsd.org> Synopsis: [ext3fs] Writing to ext3 partition causes endless loop State-Changed-From-To: open->closed State-Changed-By: kib State-Changed-When: Tue Jan 27 09:52:14 UTC 2009 State-Changed-Why: Patch is already committed to HEAD and RELENG_7. http://www.freebsd.org/cgi/query-pr.cgi?pr=131024 From linimon at FreeBSD.org Tue Jan 27 08:00:38 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Tue Jan 27 08:00:50 2009 Subject: kern/131009: [ext2fs] [hang] System freezes when attempting to copy from one mounted (USB-disk-resident) ext2 filesystem to another Message-ID: <200901271600.n0RG0aVr074282@freefall.freebsd.org> Old Synopsis: System freezes when attempting to copy from one mounted (USB-disk-resident) ext2 filesystem to another New Synopsis: [ext2fs] [hang] System freezes when attempting to copy from one mounted (USB-disk-resident) ext2 filesystem to another Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Jan 27 16:00:06 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131009 From linimon at FreeBSD.org Wed Jan 28 07:38:08 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Jan 28 07:38:14 2009 Subject: kern/131081: [zfs] User cannot delete a file when a ZFS dataset is full. Message-ID: <200901281538.n0SFc7kZ082819@freefall.freebsd.org> Old Synopsis: User cannot delete a file when a ZFS dataset is full. New Synopsis: [zfs] User cannot delete a file when a ZFS dataset is full. Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jan 28 15:37:54 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131081 From attilio at freebsd.org Wed Jan 28 11:06:12 2009 From: attilio at freebsd.org (Attilio Rao) Date: Wed Jan 28 11:06:19 2009 Subject: [PATCH] improving netncp locking Message-ID: <3bbf2fe10901281045s7e3280dep5a26df6541595cfe@mail.gmail.com> Attached there is a patch that fixes netncp locking. Actually, netncp tries to drain connections without any protection for the nc_id field (which is supposed to discriminate between a valid connection and one under draining). Also, the drain still uses loose ending LK_DRAIN. This patch adds correct locking for draining path adding an interlock, control flags, a refcount and using it accordingly. Ultimately 2 locks are switched to be sx as they don't rely on any particular lockmgr feature. The patch compiles and boots ok, but if someone could test and review it I would appreciate a lot. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: netncp.diff Type: text/x-diff Size: 14447 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090128/04458187/netncp.bin From linimon at FreeBSD.org Wed Jan 28 23:42:30 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Jan 28 23:42:41 2009 Subject: kern/131086: [ext2fs] mkfs.ext2 creates rotten partition Message-ID: <200901290742.n0T7gTK9044011@freefall.freebsd.org> Old Synopsis: mkfs.ext2 creates rotten partition New Synopsis: [ext2fs] mkfs.ext2 creates rotten partition Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 29 07:41:44 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131086 From linimon at FreeBSD.org Wed Jan 28 23:43:57 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Jan 28 23:44:03 2009 Subject: kern/131084: [xfs] xfs destroys itself after copying data Message-ID: <200901290743.n0T7huBe044078@freefall.freebsd.org> Old Synopsis: xfs destroys itself after copying data New Synopsis: [xfs] xfs destroys itself after copying data Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 29 07:43:28 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=131084 From info at videobrokers.com Fri Jan 30 04:10:45 2009 From: info at videobrokers.com (Video Brokers) Date: Fri Jan 30 04:10:54 2009 Subject: Second hand video equipment for sale. Message-ID: [1]WWW.VIDEOBROKERS.COM WE BUY & SALE USED VIDEO/BROADCAST EQUIPMENTS! Hello, Please find bellow some details regarding the equipment we have for sale at the moment. Do not hesitate to get in touch with us if what you are looking for is not listed here, let us know as well what you have for sale. VISION MIXER's : Sony DVS2000, 10 SDI inputs @ 5.000 Euros Sony DVS2000, 16 SDI inputs @ 7.000 Euros Abekas A8150, SDI @ 3.000 Euros BTS DD20, specs on request @ 8.000 Euros BTS DD30, specs on request @ 10.000 Euros BTS DD35, specs on request @ 14.000 Euros GVG 1200, SDI @ 5.000 Euros GVG 4000, specs on request @ 4.000 Euros GVG Kayak DD1, full options @21.000 Euros GVG Kayak HD200 & HD300, specs on request @ contact us for a quote Sony DVS7250 & 7350, specs on request @ contact us for a quote VTR's : Panasonic AJ-D230H, 200 original drum hours @ 1.100 Euros Panasonic AJ-D650E, 2400 original drum hours @ 1.000 Euros Panasonic AJ-D650E, with SDI, new drum "0hrs" @ 2.500 Euros Panasonic AJ-D950E, 2500 original drum hours @ 6.000 Euros Panasonic AJ-D960E, 1000 drum hours @ 7.000 Euros Panasonic AJLT-75E, 1500 original drum hours @5.500 Euros Panasonic AJLT95, new drum "0hrs" @ 9.000 Euros Panasonic AJHD1200E, 1200 original drum hours @ 9.000 Euros Panasonic AJHD1400E, 280 original drum hours @ 16.500 Euros Sony UVW1200P, details on request @ from 400 Euros Sony UVW1600P, details on request @ from 700 Euros Sony UVW1800P, details on request @ from 1.000 Euros Sony PVW2600P, details on request @ from 800 Euros Sony PVW2650P, new drum "0hrs" @ 1.500 Euros Sony PVW2800P, serviced @ 2.000 Euros Sony BVW60P, details on request @ from 400 Euros Sony BVW65P, details on request @ from 400 Euros Sony BVW70P, details on request @ from 2.000 Euros Sony BVW70P with SDI, 800 drum hours @ 2.800 Euros Sony BVW75P, details on request @ from 2.000 Euros Sony BVWD75P, 310 drum hours @ 2.800 Euros Sony DSR1P, 59 original drum hours @ 1.900 Euros Sony DSR40P, 680 original drum hours @ 1.900 Euros Sony DSR45P, 800 original drum hours @ 2.500 Euros Sony DSR60P, 900 drum hours @ 600 Euros Sony DSR80P, with SDI, 2600 original drum hours @ 2.200 Euros Sony DSR85P, with SDI, new drum "0hrs" @ 3.500 Euros Sony DSR1500AP, with fire wire and YUV, 680 original drum hours @ 3.500 Euros Sony DSR1500AP, with SDI& fire wire, 400 original drum hours @ 4.000 Euros Sony DSR2000P, 2600 original drum hours @ 5.500 Euros Sony DSR2000P, new drum "hrs" @ 7.000 Euros Sony DNWA30P, 2000 original drum hours @ 1.500 Euros Sony DNWA65P, 3000 drum hours @ 1.800 Euros Sony DNWA75P, 3500 original drum hours @ 4.500 Euros Sony DNWA220P, 2500 drum hours @ 4.000 Euros Sony DNWA225P, 2200 drum hours @ 7.000 Euros Sony J1, betacam SP and SX player, low hours @ 1.200 Euros Sony J3A, 1200 original drum hours @ 3.900 Euros Sony DVW522P, low original drum hours @ 2.500 Euros Sony DVW510P S/N 11198, 3278 drum hours @ 4.500 Euros Sony DVWA510P, 2500 drum hours @ 6.000 Euros Sony DVW500P S/N 16243, 3587 drum hours @ 15.000 Euros Sony DVWA500P S/N 10520, fully serviced, new drum "0hrs" @ 19.000 Euros Sony DVWM2000P, 300 original drum hours @ 23.000 Euros Sony JH3, 150 original drum hours, with fire wire @ 13.000 Euros Sony HDWM2000P S/N 49298, EX-DEMO, 390 original drum hours @ 33.000 Euros Sony HDWM2000P, NEW IN THE BOX @ 36.000 Euros CAMERA's & CAMCORDER's : Sony HDC1500, complete camera chain, specs on request, 16 units available @ 50.000 Euros/ unit Thomson LDK8000, complete camera chain, specs on request, 6 units available @ make an offer Sony DXCD30P, camera head @ 1.600 Euros Sony DXCD35P, camera head @ 2.000 Euros Thomson TTV1657D (4/3-16:9) complete triax chain @ 16.000 Euros Thomson LDK23HS MKII complete chain @ 38.000 Euros Panasonic AJD800P, 1400 drum hours @ 1.600 Euros Panasonic AJD610WAE, 700 drum hours @ 3.600 Euros Panasonic AJ-SDC615E, 1300 original drum hours @ 4.500 Euros Panasonic AJD910WAE, low hours @ 5.000 Euros Panasonic AGHVX200, ex-demo, 0hrs @ 3.300 Euros Panasonic AJSDX900, with AJ-VF20WE, 2550 original drum hours @ 7.000 Euros Panasonic AJHDX900, with AJ-HVF21, 1150 original drum hours @13.000 Euros Panasonic HPX-2100E, ex-demo, 4 years warranty, with view finder and microphone @ 18.700 Euros Panasonic AJ-HDC27 (varicam), 800 original drum hours @ 15.000 Euros Sony BVWD600P S/N 40358, 233 drum hours @ 2.000 Euros Sony HVR-Z1E, around 700 original drum hours @ 2.000 Euros Sony HVR-Z5E, NEW @ 3.740 Euros Sony HVR-Z7E, NEW @ 4.680 Euros Sony PMW-EX3, NEW @ 6.870 Euros Sony PMW-700, NEW @ 21.840 Euros Sony DSRPD150P, battery charger @ 1.200 Euros Sony DSRPD170P, battery charger, wide angle converter @ 1.600 Euros Sony DSR370P S/N 42129, 383 original drum hours, including Canon YH19x6.7KRS @ 3.500 Euros Sony DSR400P S/N 43512, 50 original drum hours @ 4.000 Euros Sony DSR500WSP S/N 42925, 800 original drum hours @ 3.000 Euros Sony DSR570WSP S/N 46925, 1200 original drum hours @ 4.500 Euros Sony DSR450WSP S/N 42790, 550 original drum hours @ 7.500 Euros Sony DVW700P, details on request @ from 2.000 Euros Sony DVW707P, details on request @ from 2.500 Euros Sony DNW7P, details on request @ from 2.000 Euros Sony DNW9WSP, details on request @ from 4.000 Euros Sony DNW90WSP, details on request @ from 6.000 Euros Sony DVW709WSP S/N 40090, 1317 original drum hours @ 9.000 Euros Sony DVW709WSP S/N 40011, 399 original drum hours @ 10.000 Euros Sony DVW790WS S/N 40330, 55 drum hours @ 13.500 Euros Sony DVW790WSP S/N 41929, 516 drum hours @ 15.000 Euros Sony DVW790WSP S/N 42199, 601 original drum hours @ 17.000 Euros Sony PDW530P S/N 40538, 40 original lazer hours @ 14.000 Euros Sony PDW530P S/N 60394, 18 original lazer hours @ 15.000 Euros Sony HDW730S S/N 10192, 551 original drum hours, like new ! @ 16.000 Euros Sony HDW750P S/N 40113, 1513 original drum hours, with down converter @ 17.000 Euros Sony HDW750P S/N 40112, 1521 original drum hours, with down converter @ 17.000 Euros Sony HDW790P, 70 original drum hours @ 23.000 Euros Sony HDWF900/3 S/N 12474, 1519 original drum hours @ 20.000 Euros LENSES : Canon ZSD300 & FPD400, ex-demo @ 1.500 Euros Fujinon A16x9BERM @ 800 Euros Canon J15x8BIRS @ 1.500 Euros Fujinon A15x8BEVM @ 1.500 Euros Fujinon A8.5x5.5BEVM @ 3.000 Euros Canon YJ19x9KRS @ 1.000 Euros Canon YJ12x6.5IRS @ 3.000 Euros Canon J16x8BIRS @ 2.500 Euros Canon J8x6BKRS @ 1.800 Euros Canon J8x6BIRS @ 2.500 Euros Canon J9x5.2BIRS @ 5.000 Euros Canon J11x4.5BIRS @ 7.000 Euros Canon J22x7.6IAS @ 6.000 Euros Canon J33x15IRS with lens support + remotes @ 17.000 Euros Fujinon A10x4.8BEVM @ 6.000 Euros Fujinon A13x4.5BERD @ 8.000 Euros Fujinon HA13x4.5BERM, @ 12.000 Euros Fujinon HA13x4.5BERM, EX-DEMO @ 13.000 Euros Fujinon HA20x7.8BM10 @ 13.000 Euros Fujinon HA10x5BM10 @ 13.000 Euros Canon HJ11x4.7BIRSE, NEW @ 13.000 Euros Canon HJ21x7.8BIRSD @ 11.000 Euros Canon HJ22x7.6BIRSE, EX-DEMO @ 13.000 Euros Canon HJ22x7.6BIASE, NEW @ 14.000 Euros Fujinon HA42x , perfect condition @ contact us Canon J55super, with zoom and focus + lens support @ 19.000 Euros Canon PJ70 MK1 with zoom and focus + lens support @ 24.000 Euros Canon PJ70 MKII with zoom and focus + lens support @ 34.000 Euros Canon DIGI SUPER 86 XS with zoom and focus @ 78.000 Euros Fujinon HAe 10x10 M T1.8 @ 45.000 Euros Fujinon Super prime set @ 14.000 Euros, including : HAe F5-M10 T1.5 and HAe F8-M10 T1.5 and HAe F20-M10 T1.5 VARIOUS : Sony DME3000 @ 3.000 Euros Sony DME7000 @ 6.000 Euros Sony CA701 @ 2.000 Euros Sony RMM7G @ 700 Euros Sony CCUM5P @ 900 Euros Sony CCUM7P @ 1.000 Euros Sony CA537P @ 700 Euros Snell & Wilcox TBS24D @ 2.000 Euros Pinnacle DEKO 500 @ 3.000 Euros Pinnacle DEKO 2000 @ 9.000 Euros Sony DSC1024 @ 1.000 Euros Panasonic BTLH900E @ 2.350 Euros Panasonic BTLH1700E @ 1.480 Euros Sony BVF-VC10W @ 1.700 Euros Sony LMD 1420 @ 500 Euros Sony LMD 2020 @ 600 Euros Sony PVM9L2 @ 500 Euros Sony PVM20M2, ex-demo @ 600 Euros Sony PVM20M4 SDI @ 1.600 Euros Sony BVM2016P with SDI @ 1.500 Euros Sony BVM20G1E with SDI & BKM10R @ 4.000 Euros Sony BVMD20F1E with BKM11RR & BKM21D & BKM14L @ 6.000 Euros Sony BVM-F24E, HD/SDI, 4000 operation hours @ 19.000 Euros Sony RM450 @ 600 Euros Sony PVE500 @ 900 Euros Sony BVE9100 @ 1.500 Euros Sony BVE2000 @ 1.500 Euros Tektronix 1721/1731 @ 600 Euros Tektronix SPG110 @ 400 Euros Tektronix SPG271 @ 1.000 Euros Tektronix TSG111 @ 500 Euros Fora FA320, TBC @ 500 Euros Fora FA330, TBC @ 600 Euros Vinten Vision 10 @ 1.300 Euros Vinten Vision 11, carbon fiber @ 2.000 Euros Sachtler S18+ SBMLCF @ 3.900 Euros Tektronix WFM300 @ 800 Euros Tektronix WFM601A @ 2.500 Euros Tektronix WFM5000, ex-demo @ 4.250 Euros Sony DMXE2000 @ 1.500 Euros Sony DMXE3000 @ 2.500 Euros Sony PCM7030 @ 600 Euros Sony PCM7040 @ 1.200 Euros Yamaha 03D @ 800 Euros DK AUDIO PT5210, Vari Time Digital Sync Generator @ 2.000 Euros IDX video wireless system SDI, Model: WIVI @ 2.700 Euros AccuScene VF 1280S HD view finder with zebra Black & White, compatible for F23/F35/Genesis/RED @ 9.000 Euros FOUCUS FS-100, fire store HD multiformat DVCPRO HD, 100Go @ 400 Euros Snell & Wilcox IQ MODULAR with IQADBBG and 2x IQAVDA @ 2.000 Euros EVS XT2 6 channels SD, 5x 73GO, audio analo, AES, 2x PSU cool swap, open code, multicam LSM, super motion, FX split screen, network SDTI 1.5, protocol VDCP/DD35/ODETICS/LOUTH, protocol AVSP @ 72.000 Euros Video Brokers [2]www.videobrokers.com Alexandre Villegoureix Tel : +33 (0)6.09.84.13.86 Email : [3]alex@videobrokers.fr [4]If you wish not to receive anyfirther offer from us please follow this link References 1. http://url.videobrokers.com/id.asp?l=51090-4030682-388172-966-0 2. http://url.videobrokers.com/id.asp?l=51090-4030682-388172-966-0 3. mailto:alex@videobrokers.fr 4. http://url.videobrokers.com/id.asp?l=51089-4030682-388172-966-0&id=388172-966-4030682-d8288780&res=fr From peterjeremy at optushome.com.au Sat Jan 31 23:24:41 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sat Jan 31 23:24:47 2009 Subject: Booting from ZFS raidz In-Reply-To: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> Message-ID: <20090201072432.GA25276@server.vk2pj.dyndns.org> On 2008-Dec-17 18:25:51 +0000, Doug Rabson wrote: >I've been working on adding raidz and raidz2 support to the boot code >and I have a patch which could use some testing if anyone here is >interested. This http://people.freebsd.org/~dfr/ >raidzboot-17122008.diff adds support for raidz and raidz2. The easiest >way to prepare a bootable pool is to put a GPT boot partition on each >disk that will make up the raidz pool and install gptzfsboot on the >boot partition of every drive. This sounds great so I thought I'd try it. Unfortunately, it didn't work on my degraded pool [ZFS managed to kill a disk and I thought I'd experiment]. When I tried to boot, I got: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS ZFS: unexpected object set type lld FreeBSD/i386 boot Default: tank:/boot/loader boot: The boot loader is up-to-date and was built with 'LOADER_ZFS_SUPPORT'. Any ideas? -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20090201/9169cbb9/attachment.pgp