Sure, we can pass this feedback along.
Thanks for reporting it.
Cindy
On 09/11/12 10:00, Cedric Blancher wrote:
Forwarded conversation
Subject: [developer] SUNWspro compiler bug
From: Matthew Ahrensmahr...@delphix.com
Date: 11 September 2012 06:35
To:
I speak for myself... :-)
If the real bug is in procfs, I can file a CR.
When xattrs were designed right down the hall from me,
I don't think /proc interactions were considered, which
is why I mentioned an RFE.
Thanks,
Cindy
On 07/15/12 15:59, Cedric Blancher wrote:
On 14 July 2012
I don't think that xattrs were ever intended or designed
for /proc content.
I could file an RFE for you if you wish.
Thanks,
Cindy
On 07/13/12 14:00, ольга крыжановская wrote:
Yes, accessing the files through runat works.
I think /proc (and /dev/fd, which has the same trouble but only works
.
Taking a while to wrap my head around just the Solaris 11 basics, but
enjoying it so far and looking forward to being able to deploy a ZFS
solution in the near future. Thanks for the help!
-Anh
On Mar 5, 2012, at 3:34 PM, Cindy Swearingen wrote:
Hi Anh,
I'm unclear what else might be going
Hi Anh,
I'm unclear what else might be going on but maybe we should go
back to some basics. In general, the NFS services don't start
up unless something is shared. See the example below.
Failing that, did you review the nfs-server log to identify
what the problem is:
# more
Hi Andrew,
You can use the zfs set share to respecify property=value values or
you can use the zfs -c set to remove the property values so you would
need to specify rw=value public=false, and so on.
When using zfs -c set share, I found that peeling off one property=value
at a time worked best.
I'm adding a few more tips, including the one below, to our upgrade
instructions.
Thanks for the feedback--
Cindy
On 11/17/11 19:03, Jeff wrote:
...
pfexec pkg update
Creating Plan \
pkg update: No solution was found to satisfy constraints
Plan Creation: Package solver has not found a
Hi Harry,
You might review this summary table of changes to see what else
has changed and it should point you in the right direction:
http://download.oracle.com/docs/cd/E23824_01/html/E24456/compare-1.html
If it doesn't, let us know.
Thanks,
Cindy
On 11/16/11 07:15, Harry Putnam wrote:
Hi Willi,
We will fix the support repo path error.
Can you clarify your comments below:
Are you saying that if you set the support repository correctly
to https://pkg.oracle.com/solaris/support, the command still
fails?
Thanks,
Cindy
On 11/16/11 11:40, Willi Burmeister wrote:
Hi,
I'm
, Harry Putnam wrote:
Cindy Swearingen
cindy.swearin...@oracle.com writes:
Hi Harry,
You might review this summary table of changes to see what else
has changed and it should point you in the right direction:
http://download.oracle.com/docs/cd/E23824_01/html/E24456/compare-1.html
If it doesn't
?
If you originally reinstalled an Oracle Solaris 10 system with Oracle
Solaris 11 Express and will upgrade to Oracle Solaris 11, then
including the Express info in this doc is not such a stretch. MHO.
Thanks,
Cindy
On 11/16/11 12:43, Ian Collins wrote:
On 11/17/11 04:43 AM, Cindy Swearingen wrote
Hi Brian,
Try this one:
http://download.oracle.com/docs/cd/E23824_01/html/E24456/upgrade-1.html
The main OS 11 library (English) is here:
http://download.oracle.com/docs/cd/E23824_01/index.html
Let us know how the upgrade goes.
Thanks,
Cindy
On 11/09/11 11:05, Brian Wilson wrote:
Can't
Collins wrote:
On 11/10/11 08:17 AM, Shawn Walker wrote:
On 11/09/11 11:11, Ian Collins wrote:
On 11/10/11 07:13 AM, Cindy Swearingen wrote:
Hi Brian,
Try this one:
http://download.oracle.com/docs/cd/E23824_01/html/E24456/upgrade-1.html
The main OS 11 library (English) is here:
http
Hi Ned,
The p* devices represent the fdisk partition.
The disk naming is very confusing so let's summarize:
c*t*d*p* - represents the larger fdisk partition. Do no use these
for your storage pools.
c*t*d* - represents the whole disk. Use these for your pools
except when creating a root pool
Hi Steven,
I think you are running into CR 6867013:
lucreate fails when ZFS-based zones are located at the top of zfs pools
I think the problem is that you can't use Live Upgrade if you have
zone root that is a top-level dataset.
Thanks,
Cindy
On 05/02/11 06:05, Steven Sim wrote:
Gurus;
I see now that data1 and data2 are ZFS file systems, which should have
been clear to me from your mount output.
A mounted UFS file system would look like this:
/stuff on /dev/dsk/c0t0d0s5 read/write/setuid/intr/largefiles/xattr...
ZFS file systems aren't associated with a particular device.
Xaverius,
Looks like you have a ZFS root file system on this system.
ZFS file systems are mounted automatically even in Solaris 10
releases. No need exists to add ZFS file system entries to the
/etc/vfstab file for them to mount automatically. Entries in this
file are only needed for UFS file
Hi Heinrich,
Yes, you need pool version 16 (stmf property) to use COMSTAR.
Thanks,
Cindy
On 03/17/11 16:22, Heinrich Rebehn wrote:
On Mar 17, 2011, at 9:46 PM, David Brodbeck wrote:
On Thu, Mar 17, 2011 at 1:31 PM, Ian Collins i...@ianshome.com
mailto:i...@ianshome.com wrote:
My
Hi Orvar,
I think you are running b151a and this problem was fixed on b154:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6969598
junk in format for cmdk disks
I also see a similar problem reported if this disk had a GPT label.
I don't know how to fix this, other than backing up
Hi Mike,
I would check that your hardware is functioning correctly by using these
commands:
# fmdump -eV
# iostat -En
# more /var/adm/messages
Thanks,
Cindy
On 02/14/11 05:45, Mike DeMarco wrote:
Before I upgraded I tried to mirror my root drive using Sun Volume Manager
(Disk Suites)
Hi Mike,
The root pool disks must contain a valid SMI label and a slice 0, for
example, because a long-standing limitation is that the boot information
must be contained in a slice.
If your mirrored root pool disks contain valid SMI labels, slices 0, for
example, and you applied the boot
I'm not sure I'm following. Can you display the partition tables for
both disks from the format--disk--partition--print menu?
Are you using the partitions on these disks for pools/file systems other
than the root pool? I don't recommend this configuration.
If not, then try to make sure the
We're not dead yet. :-)
We're looking into this problem and hope to republish this collection
soon to solve these issues.
Thanks for reporting this problem.
Cindy
On 02/11/11 02:50, Chavdar Ivanov wrote:
Hi,
I see the documentation forum is all but dead; as we have no current Oracle
Hi Shain,
You can't disable the system extended attributes and they shouldn't
cause any problem unless you are accessing files with these
attributes on systems that run Solaris 10 releases, which don't
understand how to translate them.
Is this is cause of the permission denied errors?
If you
:3056:handle_pair] posix1:
/smbpool/glusterfs/audio: key:SUNWattr_ro error:Permission denied
I am hoping to get some more verbose output tonight when I increase the
logging level and restart the cluster.
Thanks again,
Shain
On 01/11/2011 03:31 PM, Cindy Swearingen wrote:
Hi Shain,
You
Hi Deric,
If you boot into single-user mode, you will be prompted for the root
password or another privileged user so you need to boot from alternate
media like the installation CD.
Try the steps listed here:
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide
Recover
Hi--
Yes, see the automated installer guide, here:
http://docs.sun.com/app/docs/doc/820-6566/iediskrepo?l=ena=view
Example 4–6 Specifying an iSCSI Target
Thanks,
Cindy
On 11/17/10 10:43, carlopmart wrote:
Hi all,
Is not possible to install Solaris 11 Express onto iSCSI disk?? I don't
wrote:
On 11/17/2010 07:00 PM, Cindy Swearingen wrote:
Hi--
Yes, see the automated installer guide, here:
http://docs.sun.com/app/docs/doc/820-6566/iediskrepo?l=ena=view
Example 4–6 Specifying an iSCSI Target
Thanks,
Cindy
Thanks Cindy, but do I need to do this using automated installer
Hi Chris,
I think you are running into this bug:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6538600
pool version is not updated in the label config after zpool upgrade and
before reboot
Exporting and importing the pool or a reboot seems to clear it up.
Thanks,
Cindy
On
Hi Mike,
I think you are seeing this bug:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6538600
pool version is not updated in the label config after zpool upgrade and
before reboot
I saw strange zdb behavior after a pool upgrade on b146 and an
export/import of the pool cleared
Hi Justin,
Maybe I misunderstand your question...
When you export a pool, it becomes available for import by using
the zpool import command. For example:
1. Export tank:
# zpool export tank
2. What pools are available for import:
# zpool import
pool: tank
id: 7238661365053190141
casper@sun.com writes:
[...]
Is there a better way?
Yes.
[...]
zpool pool attach olddevice newdevice (make a
mirror)
and later, after a reboot from the new mirror (and
after installing grub)
zpool pool detach pool olddevice
Well, I'm still
32 matches
Mail list logo
