Thanks everybody for the replyies.. appreciate all your help.
Here is my understanding from all of the above:
1. The Configuration of ZFS is on all ZFS disk , so incase of the disk failure
there is less chances to loose the configuration for ZFS
2. The is no configuration file for ZFS on the Oper
On Sat, Mar 22, 2008 at 4:36 PM, Sachin Palav
<[EMAIL PROTECTED]> wrote:
> Thanks everybody for the replyies.. appreciate all your help.
>
> Here is my understanding from all of the above:
> 1. The Configuration of ZFS is on all ZFS disk , so incase of the disk
> failure there is less chances to
Sachin Palav indiatimes.com> writes:
>
> 3. Currently there no command that prints the entire configuration of ZFS.
Well there _is_ a command to show all (and only) the dataset properties
that have been manually "zfs set":
$ zfs get -s local all
For the pool properties, zpool has no "-s loca
Hi All,
This is a step-by-step procedure to upgrade Solaris 10 06/06 (u2) to Solaris 10
08/07 (u4).
Before any attempt to upgrade you will need to install 'at least' the
Recommended patches dated March 2008.
- The Kernel level of the u2 system must be 120011-14.
- The zones will have to be moved
Hi all,
I'm migrating to a new laptop from one which has had hardware issues lately. I
kept my home directory on zfs, so in theory it should be straightforward to
send/receive, but I've had issues. I've moved the disk out of the faulty
system, though I saw the same issue there.
The behavior
So this will actually work?
On Sat, Mar 22, 2008 at 5:58 PM, Vahid Moghaddasi <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> This is a step-by-step procedure to upgrade Solaris 10 06/06 (u2) to Solaris
> 10 08/07 (u4).
> Before any attempt to upgrade you will need to install 'at least' the
> Recomm
One update to this, I tried a scrub. This found a number of errors on old
snapshots (long story, I'd once done a zpool replace from an old disk with
hardware errors to this disk). I destroyed the snapshots since they weren't
needed. The snapshot I was trying to send did not have any errors.
One more scrub later, and now the snapshot I was trying to send,
@laptopmigration, is now showing errors but the errors on the old snapshots are
gone, since I destroyed the snapshots.
Is this expected behavior? Should the errors only show on one snapshot at a
time? I have a suspicion that if
On Sat, Mar 22, 2008 at 11:33 PM, Matt Ingenthron <[EMAIL PROTECTED]>
wrote:
> One more scrub later, and now the snapshot I was trying to send,
> @laptopmigration, is now showing errors but the errors on the old snapshots
> are gone, since I destroyed the snapshots.
>
> Is this expected behavior?
I am running sol 10 on a Sun Enterprise 220R (2 X UltraSPARC-II
450MHz) with 1G real memory.
It crashed twice in 5 days. Here are the mdb output
(root)@syslog1:/var/crash/syslog1# mdb -k unix.0 vmcore.0
Loading modules: [ unix krtld genunix specfs dtrace ufs sd pcipsy ip
hook neti sctp arp usba f
First crash seems to match BUG ID 6439484
Second crash seems to match BUG ID 6523336
I see both of them are closed without any recommendation.
On Sun, Mar 23, 2008 at 1:22 AM, Asif Iqbal <[EMAIL PROTECTED]> wrote:
> I am running sol 10 on a Sun Enterprise 220R (2 X UltraSPARC-II
> 450MHz) with 1
Second crash actually matches bug id 6618522
On Sun, Mar 23, 2008 at 1:28 AM, Asif Iqbal <[EMAIL PROTECTED]> wrote:
> First crash seems to match BUG ID 6439484
> Second crash seems to match BUG ID 6523336
>
> I see both of them are closed without any recommendation.
>
>
>
> On Sun, Mar 23, 2008
12 matches
Mail list logo