I used the default while creating zpool with one disk drive. I guess it is a
RAID 0 configuration.
Thanks,
Giri
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/lis
> Hi Giridhar,
>
> The size reported by ls can include things like holes
> in the file. What space usage does the zfs(1M)
> command report for the filesystem?
>
> Adam
>
> On Dec 16, 2009, at 10:33 PM, Giridhar K R wrote:
>
> > Hi,
> >
>
Hi,
Reposting as I have not gotten any response.
Here is the issue. I created a zpool with 64k recordsize and enabled dedupe on
it.
-->zpool create -O recordsize=64k TestPool device1
-->zfs set dedup=on TestPool
I copied files onto this pool over nfs from a windows client.
Here is the output o
As I have noted above after editing the initial post, its the same locally too.
>>I found that the "ls -l" on the zpool also reports 51,193,782,290 bytes
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.or
Hi,
Created a zpool with 64k recordsize and enabled dedupe on it.
zpool create -O recordsize=64k TestPool device1
zfs set dedup=on TestPool
I copied files onto this pool over nfs from a windows client.
Here is the output of zpool list
Prompt:~# zpool list
NAME SIZE ALLOC FREECAP
