The zpool.cache file makes clustering complex. {Assume the man page is
still correct}
From the zpool man page:
cachefile=path | "none"
Controls the location of where the pool configuration is cached.
Discovering all pools on system startup requires a cached copy of the
configuration data that
On Tue, Mar 24, 2009 at 00:21, Tim wrote:
>
>
> On Mon, Mar 23, 2009 at 4:45 PM, Mattias Pantzare
> wrote:
>>
>>
>> If I put my disks on a diffrent controler zfs won't find them when I
>> boot. That is bad. It is also an extra level of complexity.
>
> Correct me if I'm wrong, but wading through a
Cross-posting to the public ZFS discussion alias.
There's nothing here that requires confidentiallity, and
the public alias is a much broader audience with a larger
number of experienced ZFS users...
As to the issue - what is the free space disparity
across the pools? Is the one particular pool
On Mon, Mar 23, 2009 at 4:45 PM, Mattias Pantzare wrote:
>
>
> If I put my disks on a diffrent controler zfs won't find them when I
> boot. That is bad. It is also an extra level of complexity.
>
Correct me if I'm wrong, but wading through all of your comments, I believe
what you would like to se
On Mon, Mar 23, 2009 at 22:15, Richard Elling wrote:
> Mattias Pantzare wrote:
I suggest ZFS at boot should (multi-threaded) scan every disk for ZFS
disks, and import the ones with the correct host name and with a import
flag
set, without using the cache file. Maybe just u
Mattias Pantzare wrote:
I suggest ZFS at boot should (multi-threaded) scan every disk for ZFS
disks, and import the ones with the correct host name and with a import flag
set, without using the cache file. Maybe just use the cache file for non-EFI
disk/partitions, but without the storing the pool
>> I suggest ZFS at boot should (multi-threaded) scan every disk for ZFS
>> disks, and import the ones with the correct host name and with a import flag
>> set, without using the cache file. Maybe just use the cache file for non-EFI
>> disk/partitions, but without the storing the pool name, but you
Damon Atkins wrote:
Do we still need the zpool.cache still. I believe early versions of
zpool used the cache to remember what zpools to import at boot.
Yes.
I understand newer versions of zfs still use the cache but also check
to see if the pool contains the correct host name of the server, a
Do we still need the zpool.cache still. I believe early versions of
zpool used the cache to remember what zpools to import at boot.
I understand newer versions of zfs still use the cache but also check to
see if the pool contains the correct host name of the server, and will
only import if the
On Sat, Mar 14, 2009 at 8:25 PM, Richard Elling wrote:
> Florian Ermisch wrote:
>
>> Richard Elling schrieb:
>> [...]
>>
>>> ZFS maintains a cache of what pools were imported so that at boot time,
>>> it will automatically try to re-import the pool. The file is
>>> /etc/zfs/zpool.cache
>>> and yo
10 matches
Mail list logo
