On Tue, 24 Jul 2012, Kostas Oikonomou wrote:
I am attempting to upgrade from 151a3 to 151a5. But the update fails:
$ pfexec pkg update -v --accept
Creating Plan /
pkg update: The requested change to the system attempts to install multiple
actions
for link 'usr/gnu/lib/libiconv.so' with confl
On 07/25/2012 02:26 PM, Jim Klimov wrote:
>
> I think it is a bug for the system to hang upon requests to a
> faulty pool - unless this behavior was requested with "failmode".
> From what I gather below, the box itself no longer hangs upon
> hitting problems (but some zfs/zpool commands still do?)
2012-07-25 19:16, Ray Arachelian wrote:
First of all, I'm glad my suggestions have helped, at least :)
On 07/25/2012 10:42 AM, Gregory Youngblood wrote:
Assuming the faulted drive or pool is not rpool, containing required
files for the system, why should a faulty drive or pool hang the
entire
On Jul 24, 2012, at 9:11 AM, Jason Matthews wrote:
> are you missing a zero to the left of the decimal place?
Been there, done that, wrote a whitepaper. Add 2 zeros.
-- richard
> Sent from Jasons' hand held
>
> On Jul 23, 2012, at 8:57 PM, "John T. Bittner" wrote:
>
>> Subject: ZFS and AVS gu
On 24 July 2012 17:11, Jason Matthews wrote:
>
> are you missing a zero to the left of the decimal place?
For a couple of hours' work?
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/open
On Wed, Jul 11, 2012 at 07:26:45AM -0400, James Carlson wrote:
> Weird. That looks a whole lot like this bug:
>
> http://wesunsolve.net/bugid/id/6646104
>
> which was fixed long ago.
So my system continues to work fine. I scrub weekly again with no
errors. Is there any way to clear this errant
On 07/25/2012 10:42 AM, Gregory Youngblood wrote:
> Assuming the faulted drive or pool is not rpool, containing required
> files for the system, why should a faulty drive or pool hang the
> entire box? Why can't the system return an error and continue? Thanks,
> Greg Sent from my iPad On Jul 25, 20
> I then reran my rsync script and I see it hung the box in the same spot,
This is the part I am curious about, reading from a disk hanging the box, or
even writing. I have seen this in the distant past but fortunately it hasn't
bit me for quite some time. I believe it was Solaris 10 that I fir
Hi Milan,
I think "oi-sfe" is just a name (alias) I had given to the
"sfe" publisher when I set it up the first time. Later I
must have changed it to "sfe". You notice that "oi-sfe" has
version 147 packages.
But I didn't know that the system would use my alias for the
publisher and thus c
On 07/25/2012 02:45 AM, Jim Klimov wrote:
>
> If your pool gets imported upon system startup, and can't be
> exported nor accessed, Ray might want to remove the zfs-pool
> reference file /etc/zfs/zpool.cache, so only rpool gets imported
> upon boot. Then, to prevent adding the problematic pool from
So, I found a way to mount the zpool's volume read only.
The problem was with the cached view of the zpools here:
/etc/zfs/zpool.cache
Deleting that file and rebooting the host got rid of the locks on the
zpool - doing this however means all your zpools will be offline except
the rpool, until you
I tried 2 things:
1. create an iSCSI target with napp-it on Openindiana
2. create an iSCSI target on Solaris 10
Both things I tried resulted in a working iSCSI drive, hip hay...
Then I mount these drives from a Windows 7 laptop, the drive is identified
and I am asked to format it.
That works too
Hi,
I am not sure from where is your oi-sfe package comming from. But
clearly you cannot use two source of SFE packages, one of your publisher
(sfe or oi-sfe) has to go (and all its packages have to be uninstalled
from your system).
I am in slow progress to refresh http://pkg.openindiana.org
13 matches
Mail list logo
