2012-01-17 18:16, Albert Shih ?????:> Hi all.
>
> I''m totale newbie on ZFS so if I ask some stupid question, please
don''t
> send some angry mail to this mailing list, send-it directly to me ;-)
>
> Well I''ve a Dell server running FreeBSD 9.0 with 4 MD1200 with 48
disks.
> It''s connect through a LSI card. So I can see all /dev/da0 -->
/dev/da47.
>
> I''ve create a zpool with 4 raidz2 (one for each MD1200).
>
> After that I re-install the server (I put some wrong swap size), and I
> don''t find my zpool at all.
>
> Is that normal ?
Technically - yes. I am not sure how it''s done in FreeBSD, but
in Solaris known ZFS pool lists are saved in a special "cache
file" /etc/zfs/zpool.cache. These pools are automatically
imported during boot, unless they seem to be used by another
system (last pool importer''s hostid/hostname is different from
current operating environment''s id/name).
You may have several problems:
1) Absent cache file - probable if you reinstalled everything;
2) Cache file present, but hostids differ, so automatic import
safely refuses to import a potentially busy pool.
3) Other problems, such as drivers, which don''t let your current
OS see the storage devices/HBAs/etc.
In Solaris you would at this point run "zpool import" to scan
the storage hardware and see a list of pools that the system
knows of and can access. The list should show pool layouts
(component devices), pool GUID and name, and whether hostids
differ. Example:
# zpool import
pool: rpool-fix
id: 12076177533503245216
state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier
and the ''-f'' flag.
see: http://www.sun.com/msg/ZFS-8000-EY
config:
rpool-fix ONLINE
c4t1d0s0 ONLINE
If you''re certain that the pool is not used by anyone, such as
on shared mutipathed storage hardware, you can import it (and
by Solaris default it would be saved into cache file for later
automatic imports-on-boot):
# zpool import -f rpool-fix
If you need to rename the pool, i.e. another one with the same
name exists already, you can use the GUID and this syntax:
# zpool import -f 12076177533503245216 rpool-backup
Finally, you can use an "alternate root" which will be prepended
to all automatic mountpoints so that this pool does not interfere
with your running system; this also automatically disables adding
the pool to cache file:
# zpool import -R /RPOOL-BACKUP -f 12076177533503245216 rpool-backup
Hope these tips help you,
//Jim Klimov