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
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
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 system
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 not
+1
On Mon, Mar 23, 2009 at 8:43 PM, Damon Atkins damon.atk...@yahoo.com.au wrote:
PS it would be nice to have a zpool diskinfo devicepath 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
On Sat, Mar 14, 2009 at 8:25 PM, Richard Elling richard.ell...@gmail.comwrote:
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
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
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,
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 should
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
On Mon, Mar 23, 2009 at 22:15, Richard Elling richard.ell...@gmail.com 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
On Mon, Mar 23, 2009 at 4:45 PM, Mattias Pantzare pantz...@gmail.comwrote:
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
On Tue, Mar 24, 2009 at 00:21, Tim t...@tcsac.net wrote:
On Mon, Mar 23, 2009 at 4:45 PM, Mattias Pantzare pantz...@gmail.com
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,
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
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 you can view its contents by using zdb -C
If the current state of affairs does not match the cache, then
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 you can view its contents by using zdb -C
If the current state of affairs does
IMPORTANT: This message is private and confidential. If you have received this
message in error, please notify us and remove it from your system.
Hello,
I have two USB-drives connected to my PC with an zpool on each, one
called TANK, the other IOMEGA. After some problems this morning I
comment below...
Stefan Olsson wrote:
IMPORTANT: This message is private and confidential. If you have received this
message in error, please notify us and remove it from your system.
please notify your lawyers that this message is now on the internet and
publically archived forever :-)
18 matches
Mail list logo
