Date: Sat, 17 Jul 2010 10:12:10 -0700 From: Freddie Cash <fjwcash@gmail.com> To: freebsd-current@freebsd.org Subject: Re: [HEADSUP] ZFS version 15 committed to head Message-ID: <AANLkTikusWLS-3lZpY62cw2XxTdAQTG5KtFfrU29hG_W@mail.gmail.com> In-Reply-To: <20100717105134.GB13626@lordsith.net> References: <4C3C7202.7090103@FreeBSD.org> <20100717101459.GA13626@lordsith.net> <9E4FCF4C-7A69-426E-9F39-B5487D4CB07C@lassitu.de> <20100717105134.GB13626@lordsith.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 17, 2010 at 3:51 AM, Marco van Lienen <marco+freebsd-current@lordsith.net> wrote: > On Sat, Jul 17, 2010 at 12:25:56PM +0200, you (Stefan Bethke) sent the following to the -current list: >> Am 17.07.2010 um 12:14 schrieb Marco van Lienen: >> >> > # zpool list pool1 >> > NAME SIZE USED AVAIL CAP HEALTH ALTROOT >> > pool1 5.44T 147K 5.44T 0% ONLINE - >> ... >> > zfs list however only shows: >> > # zfs list pool1 >> > NAME USED AVAIL REFER MOUNTPOINT >> > pool1 91.9K 3.56T 28.0K /pool1 >> > >> > I just lost the space of an entire hdd! >> >> zpool always shows the raw capacity (without redundancy), zfs the actual available capacity. > > I have read many things about those differences, but why then does zfs on opensolaris report more available space whereas FreeBSD does not? > That would imply that my friend running osol build 117 couldn't fill up his raidz pool past the 3.56T. You used different commands to check the disk space on OSol (zpool vs df). Try the same commands on both FreeBSD and OSol (zpool and zfs) and you'll see the same results. df works differently on OSol than it does on FreeBSD, you can't compare them. -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikusWLS-3lZpY62cw2XxTdAQTG5KtFfrU29hG_W>