On Sun, Oct 5, 2014 at 11:20 PM, Digimer wrote:
> To answer this question using my use-case;
>
> I build HA clusters, and I want to make sure that physical port X on all
> nodes have the same device name. Biosdevname tries to address this, but
> doesn't work all the time.
>
> Further, in my case,
gAjJQUN2QaDO8t
> Rc+/zY2aAvP7vJ1rZtiEdt4he+wRWYCsV7olb2wq2/G+i+8FT14huRpYVufyMwLR
> VpN/sknu1KNc5fuIY6MTGYUoGDgcgCe3zy77e4cqo5IvPUNyPNfh2+X5H5xwfYaq
> pvQi6za9U2Gnlj3D65pCwI5svBWbPVNkdQO83xXNlyBhKqEqV1utqG4G5uiOusoM
> 6EIZZ9lNlLO/3PqUkg6d77HTowsT73qOmAa4KT46iZ1mnB/pibwglt8rxpAieDOD
> 3G3QSc
ed 0 overruns 0 frame 0
TX packets 74 bytes 11580 (11.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth1: flags=4163 mtu 1500
inet 172.16.154.10 netmask 255.255.255.0 broadcast 10.30.1.255
inet6 fe80::a00:27ff:fe54:1d3d prefixlen 64 scop
have noticed
a significant degrade in performance on systems running at 75-80 % of their
pool capacity. I understand that the nature of COW will increase
fragmentation. On large storages though 70% out of 100TB means that you
have to always maintain 30TB free which is not a small numb
gh I don't know if there's
> a consistent "freeze point". (what about ongoing writes?) Not sure about
> removing HDDs in a volume with XFS.
>
> Not as sure about ZFS' stability on Linux (those who run direct Unix
> derivatives seem to rave ab
5 matches
Mail list logo
