The question is, if you *temporarily* migrate your zones to UFS to install the
big bad S10u4 patch, and migrate back to ZFS afterwards, will patches work
after that? A better way to say that is, have we resolved this patch problem
with zoneroot on zfs for S10u4?
Tommy
This message posted
[EMAIL PROTECTED] said:
That link specifically mentions new Solaris 10 release, so I am assuming
that means going from like u4 to Sol 10 u5, and that shouldn't cause a
problem when doing plain patchadd's (w/o live upgrade). If so, then I am fine
with those warnings and can use zfs with zones'
I have pool called data.
I have zones configured in that pool. The zonepath is: /data/zone1/fs.
(/data/zone1 itself is not used for anything else, by anyone, and has no other
data.) There are no datasets being delegated to this zone.
I want to create a snapshot that I would want to make
Anil Jangity wrote:
I have pool called data.
I have zones configured in that pool. The zonepath is: /data/zone1/fs.
(/data/zone1 itself is not used for anything else, by anyone, and has no
other data.) There are no datasets being delegated to this zone.
I want to create a snapshot that I
Anil Jangity wrote:
I have pool called data.
I have zones configured in that pool. The zonepath is: /data/zone1/fs.
(/data/zone1 itself is not used for anything else, by anyone, and has no
other data.) There are no datasets being delegated to this zone.
I want to create a snapshot that
Thanks James/John!
That link specifically mentions new Solaris 10 release, so I am assuming that
means going from like u4 to Sol 10 u5, and that shouldn't cause a problem when
doing plain patchadd's (w/o live upgrade). If so, then I am fine with those
warnings and can use zfs with zones' path.
James C. McPherson wrote:
Anil Jangity wrote:
I have pool called data.
I have zones configured in that pool. The zonepath is: /data/zone1/fs.
(/data/zone1 itself is not used for anything else, by anyone, and has no
other data.) There are no datasets being delegated to this zone.
I want
Ian Collins wrote:
...
I don't know if anything else breaks when you do this, but if you are
building software in a zone on a lofs filesystem, dmake hangs. Regular
make works fine.
The output from truss is:
stat64(/export/home, 0x08045B60) = 0
llseek(8, 0, SEEK_CUR) = 0
llseek(8, 0,
James C. McPherson wrote:
Ian Collins wrote:
...
I don't know if anything else breaks when you do this, but if you are
building software in a zone on a lofs filesystem, dmake hangs. Regular
make works fine.
The output from truss is:
stat64(/export/home, 0x08045B60) = 0
llseek(8, 0,
Ian Collins wrote:
James C. McPherson wrote:
Ian Collins wrote:
...
I don't know if anything else breaks when you do this, but if you are
building software in a zone on a lofs filesystem, dmake hangs. Regular
make works fine.
The output from truss is:
stat64(/export/home, 0x08045B60) =
10 matches
Mail list logo
