Date: Tue, 8 Jul 2008 22:13:27 +0200 From: CZUCZY Gergely <phoemix@harmless.hu> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-fs@freebsd.org Subject: Re: Thinking of using ZFS/FBSD for a backup system Message-ID: <20080708221327.5c1d0e92@mort.in.publishing.hu> In-Reply-To: <4873C4FA.2020004@FreeBSD.org> References: <bd9320b30807072315x105cf058tf9f952f0f5bb2a6a@mail.gmail.com> <20080708100701.57031cda@twoflower.in.publishing.hu> <bd9320b30807080131j5e0e02a4y3231d7bfa1738517@mail.gmail.com> <4873C4FA.2020004@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/KaEqPRBplu5.ZRh+=81Qmdz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Yes Kris, but you've forgot something quite important. What you've just showed is -CURRENT, and how does that thumb-rule is about branches and (semi-)production systems?=20 My faint memories say something like "don't never ever even think of running -CURRENT on a production box", in a polite way. ZFS can be stable on -CURRENT but it's till -CURRENT, with its issues as a production system. So, the last we can go about a backup box is -STABLE, but i also wouldn't prefer that one, if I can. -RELEASE and patches for production, to be safe. Give us a stable ZFS in -RELEASE and -STABLE and we will be statisfied and happy. -CURRENT is still not a way for production boxes, that's asking for trouble. I've finetuned ZFS as much as I could, I've read every little tiny bit of hint/information/whatever that was available and I couldn't get rid of those kmem_size panics in -RELEASE and -STABLE. On Tue, 08 Jul 2008 21:50:18 +0200 Kris Kennaway <kris@FreeBSD.org> wrote: > mike wrote: > > On 7/8/08, CZUCZY Gergely <phoemix@harmless.hu> wrote: > >=20 > >> Regardless of this, the system worked quite well. If ZFS were > >> stable, this easily could be our backup system. ZFS is great, > >> awesome, but a bit unreliable on FreeBSD, still needs some work. > >=20 > > Really? I thought ZFS for basic things was not too bad in FBSD now. > >=20 > > By basic I mean simple filesystem creation, snapshots and normal > > devices. Not some crazy SAN LUNs and weird volume management stuff. > >=20 > > I would really love to use FBSD as opposed to a Solaris derivative, > > since I know nothing about them and I'd have to dedicate a machine > > for it at home. Hrm. I wonder if I could just get by running a > > Solaris derivative inside of a VM in VMware or something. >=20 > ZFS needs careful memory tuning, but really, it's otherwise stable > and it can be done. >=20 > (ports-i386:~>sysctl hw.ncpu > hw.ncpu: 4 > (ports-i386:~)> sysctl hw.physmem > hw.physmem: 4275478528 > (ports-i386:~)> uname -a > FreeBSD pointyhat.freebsd.org 8.0-CURRENT FreeBSD 8.0-CURRENT #31: > Wed Jun 25 19:40:40 UTC 2008=20 > kris@pointyhat.freebsd.org:/usr/src/sys.cvs/amd64/compile/POINTYHAT > amd64 (ports-i386:~)> cat /boot/loader.conf > vfs.zfs.prefetch_disable=3D1 > vm.kmem_size=3D1572864000 >=20 > This machine is highly disk loaded, with 1.08TB of disk, a load > average usually between 8-30, currently hosting 94 ZFS filesystems, > 898 snapshots, and making heavy use of ZFS features like cloning,=20 > incremental snapshot send/receive, etc. The disk workload is highly=20 > vnode-intensive, involving concurrent rsyncs over trees containing=20 > hundreds of thousands of files, busy NFS exports to about 40 clients,=20 > cvs updates, etc, constantly cycling through millions of vnodes. >=20 > It works just fine. >=20 > Kris --=20 Sincerely, Gergely CZUCZY, Harmless Digital mailto: gergely.czuczy@harmless.hu Legacy software is software that works. --Sig_/KaEqPRBplu5.ZRh+=81Qmdz Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFIc8pqzrC0WyuMkpsRAj4MAKCm0u7GAlrNHmURNtDT/e1nOkyItQCfa+h0 yKN1cUk+HTkBtRULHij0TR0= =Iuzq -----END PGP SIGNATURE----- --Sig_/KaEqPRBplu5.ZRh+=81Qmdz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080708221327.5c1d0e92>