On Thu, Jan 5, 2012 at 7:17 PM, Ivan Rodriguez wrote:
> Dear list,
>
> I'm about to upgrade a zpool from 10 to 29 version, I suppose that
> this upgrade will improve several performance issues that are present
> on 10, however
> inside that pool we have several zfs filesystems all of them are
>
On Sat, 7 Jan 2012, Jim Klimov wrote:
I believe in this case it might make sense to boot the
target system from this BootCD and use "zpool upgrade"
from this OS image. This way you can be more sure that
your recovery software (Solaris BootCD) would be helpful :)
Also keep in mind that it would
2012-01-06 17:49, Edward Ned Harvey пишет:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Ivan Rodriguez
Dear list,
I'm about to upgrade a zpool from 10 to 29 version, I suppose that
this upgrade will improve several performance issues tha
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Ivan Rodriguez
>
> Dear list,
>
> I'm about to upgrade a zpool from 10 to 29 version, I suppose that
> this upgrade will improve several performance issues that are present
> on 10, however
>
Hi Gary,
I will file a bug to track the zfs upgrade/device busy problem.
We use beadm or lucreate to upgrade the root BE so we generally don't
have to do an in-place root dataset replacement.
Thanks,
Cindy
On 07/29/10 17:03, Gary Mills wrote:
On Thu, Jul 29, 2010 at 10:26:14PM +0200, Pawel J
On Thu, Jul 29, 2010 at 10:26:14PM +0200, Pawel Jakub Dawidek wrote:
> On Thu, Jul 29, 2010 at 12:00:08PM -0600, Cindy Swearingen wrote:
> >
> > I found a similar zfs upgrade failure with the device busy error, which
> > I believe was caused by a file system mounted under another file system.
> >
On Thu, Jul 29, 2010 at 12:00:08PM -0600, Cindy Swearingen wrote:
> Hi Gary,
>
> I found a similar zfs upgrade failure with the device busy error, which
> I believe was caused by a file system mounted under another file system.
>
> If this is the cause, I will file a bug or find an existing one.
Hi Gary,
I found a similar zfs upgrade failure with the device busy error, which
I believe was caused by a file system mounted under another file system.
If this is the cause, I will file a bug or find an existing one.
The workaround is to unmount the nested file systems and upgrade them
indivi
Hi Gary,
This should just work without having to do anything.
Looks like a bug but I haven't seen this problem before.
Anything unusual about the mount points for the file systems
identified below?
Thanks,
Cindy
On 07/29/10 07:07, Gary Mills wrote:
Zpool upgrade on this system went fine, bu
James Lever wrote:
Is there a way to upgrade my current ZFS version. I show the version could
be as high as 22.
The version of Solaris you are running only suport ZFS versions up to version
15 as demonstrated by your zfs upgrade -v output. You probably need a newer
version of Solaris, b
Hi John,
On 08/01/2010, at 7:19 AM, john_dil...@blm.gov wrote:
> Is there a way to upgrade my current ZFS version. I show the version could
> be as high as 22.
The version of Solaris you are running only suport ZFS versions up to version
15 as demonstrated by your zfs upgrade -v output. You pr
seems, my problem is unrelated.
after disabling the gui and working console only, i see no freezes. so it must
be a problem of the desktop/X environment and not kernel/zfs issue.
sorry for the noise.
--
This message posted from opensolaris.org
___
zfs
i have a problem which is perhaps related.
i installed opensolaris snv_130.
after adding 4 additional disks and creating a raidz on them with
compression=gzip and dedup enabled, i got reproducable system freeze (not sure,
but the desktop/mouse-coursor froze) directly after login - without active
Colin Johnson wrote:
> I was having CIFs problems on my Mac so I upgrade to build 105.
> After getting all my shares populated with data I ran zpool scrub on
> the raidz array and it told me the version was out of date so I
> upgraded.
>
> One of my shares is now inaccessible and I cannot even
14 matches
Mail list logo