Hi Cindy,
I'll investigate more next week since I'm in a hurry to leave, but one
point now:
> I'm no device expert but we see this problem when firmware updates or
> other device/controller changes change the device ID associated with
> the devices in the pool.
This is the internal disk in a lap
Hi Rainer,
I'm no device expert but we see this problem when firmware updates or
other device/controller changes change the device ID associated with
the devices in the pool.
In general, ZFS can handle controller/device changes if the driver
generates or fabricates device IDs. You can view devic
Sean,
> I am glad it helped; but removing anything from /dev/*dsk is a kludge that
> cannot be accepted/condoned/supported.
no doubt about this: two parts of the kernel (zfs vs. devfs?) disagreeing
about devices mustn't happen.
Rainer
--
Rainer,
devfsadm -C alone didn't make a difference, but clearing out /dev/*dsk
and running devfsadm -Cv did help.
I am glad it helped; but removing anything from /dev/*dsk is a kludge
that cannot be accepted/condoned/supported.
Regards... Sean.
__
Mark J Musante writes:
> On Fri, 27 Aug 2010, Rainer Orth wrote:
>> zpool status thinks rpool is on c1t0d0s3, while format (and the kernel)
>> correctly believe it's c11t0d0(s3) instead.
>>
>> Any suggestions?
>
> Try removing the symlinks or using 'devfsadm -C' as suggested here:
>
> https://def
LaoTsao 老曹 writes:
> may be boot a livecd then export and import the zpool?
I've already tried all sorts of contortions to regenerate
/etc/path_to_inst to no avail. This is simply a case of `should not
happen'.
Rainer
--
---
On Fri, 27 Aug 2010, Rainer Orth wrote:
zpool status thinks rpool is on c1t0d0s3, while format (and the kernel)
correctly believe it's c11t0d0(s3) instead.
Any suggestions?
Try removing the symlinks or using 'devfsadm -C' as suggested here:
https://defect.opensolaris.org/bz/show_bug.cgi?id=14
hi
may be boot a livecd then export and import the zpool?
regards
On 8/27/2010 8:27 AM, Rainer Orth wrote:
For quite some time I'm bitten by the fact that on my laptop (currently
running self-built snv_147) zpool status rpool and format disagree about
the device name of the root disk:
r...@mas
For quite some time I'm bitten by the fact that on my laptop (currently
running self-built snv_147) zpool status rpool and format disagree about
the device name of the root disk:
r...@masaya 14 > zpool status rpool
pool: rpool
state: ONLINE
status: The pool is formatted using an older on-disk f
