+1
On Mon, Mar 23, 2009 at 8:43 PM, Damon Atkins wrote:
> PS it would be nice to have a zpool diskinfo reports if the
> device belongs to a zpool imported or not, and all the details about any
> zpool it can find on the disk. e.g. file-systems (zdb is only for ZFS
> "engineers" says the man pa
> MP> It would be nice to be able to move disks around when a system is
> MP> powered off and not have to worry about a "cache" when I boot.
>
> You don't have to unless you are talking about share disks and
> importing a pool on another system while the original is powered off
> and the pool was n
Hello Mattias,
Monday, March 23, 2009, 9:08:53 PM, you wrote:
MP> It would be nice to be able to move disks around when a system is
MP> powered off and not have to worry about a "cache" when I boot.
You don't have to unless you are talking about share disks and
importing a pool on another syste
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 tha
Damon Atkins wrote:
The zpool.cache file makes clustering complex. {Assume the man page is
still correct}
The man page is correct. zpool.cache helps make clustering feasible
because it differentiates those file systems which are of interest from
those which are not. This is particularly impor
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
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
13 matches
Mail list logo
