Reoccuring ZFS performance problems
Adrian Gschwend
ml-ktk at netlabs.org
Tue Mar 11 08:25:46 UTC 2014
On 11.03.14 03:16, Adam Vande More wrote:
Hi Adam,
> does not look like:
>
> 34 419430333 vtbd0 GPT (200G)
> 34 128 1 freebsd-boot (64k)
> 162 8388608 2 freebsd-swap (4.0G)
> 8388770 411041597 3 freebsd-zfs (196G)
>
>
> The question remains unanswered. swapinfo(8) will show the the swap
> device in use, and you can use that information to determine if it is
> ZFS backed. There was a swap device listed in your earlier post, but
> not enough info to determine what if it's the underlying block device.
swapinfo:
Device 512-blocks Used Avail Capacity
/dev/gptid/e4112d88-89ca-11e2-a 8388608 45592 8343016 1%
looks like the gptid is truncated but gpart list shows:
. Name: vtbd0p2
Mediasize: 4294967296 (4.0G)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 82944
Mode: r1w1e1
rawuuid: e4112d88-89ca-11e2-a867-3264262b9894
rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 4294967296
offset: 82944
type: freebsd-swap
index: 2
end: 8388769
start: 162
# zpool status
pool: tank
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
vtbd0p3 ONLINE 0 0 0
so I guess it is indeed not zfs, right?
regards
Adrian
More information about the freebsd-fs
mailing list