What does vmstat look like ?
Also zpool iostat 1.
Do you have any disk based swap ?
One best practice we probably will be coming out with is to
configure at least physmem of swap with ZFS (at least as of
this release).
The partly hung system could be this :
On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many applications including KDE use
''+' to encode paths (replacing blanks
On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many applications including KDE use
''+' to encode paths (replacing blanks
On 6/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many
Holger Berger wrote:
On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many applications including KDE use
''+' to encode
Erik Trimble wrote:
That is, start out with adding the ability to differentiate between
access policy in a vdev. Generally, we're talking only about mirror
vdevs right now. Later on, we can consider the ability to migrate data
based on performance, but a lot of this has to take into
What throughput do you get for the full untar (untared size / elapse time) ?
# tar xf thunderbird-1.5.0.4-source.tar 2.77s user
35.36s system 33% cpu 1:54.19
260M/114 =~ 2.28 MB/s on this IDE disk
IDE disk?
Maybe it's this sparc ide/ata driver issue:
Bug ID: 6421427
Synopsis: netra x1
On Tue, Jun 20, 2006 at 09:32:58AM -0700, Richard Elling wrote:
Flash is (can be) a bit more sophisticated. The problem is that they
have a limited write endurance -- typically spec'ed at 100k writes to
any single bit. The good flash drives use block relocation, spares, and
write spreading
On Tue, Jun 20, 2006 at 11:17:42AM -0700, Jonathan Adams wrote:
On Tue, Jun 20, 2006 at 09:32:58AM -0700, Richard Elling wrote:
Flash is (can be) a bit more sophisticated. The problem is that they
have a limited write endurance -- typically spec'ed at 100k writes to
any single bit. The
Jonathan Adams wrote:
On Tue, Jun 20, 2006 at 09:32:58AM -0700, Richard Elling wrote:
Flash is (can be) a bit more sophisticated. The problem is that they
have a limited write endurance -- typically spec'ed at 100k writes to
any single bit. The good flash drives use block relocation,
There are still a few problems in docs.sun.com.
If you go to the zones(5) manpage and click on any link, it says Error: The
requested document could not be found.
I think there was also a link in one of the zones commands or libc functions
that pointed to the wrong manpage, but I don't
Hi Ricardo,
I just tested most of the links from the zones.5 man page on
docs.sun.com and they all seem to be working now.
Outages occurred a couple of weeks ago but everything seems to be
working now.
Please let me know if you have any more problems with docs.sun.com and
I'll file a service
Also, options such as -nomtime and -noctime have been introduced
alongside -noatime in some free operating systems to limit the amount
of meta data that gets written back to disk.
Those seem rather pointless. (mtime and ctime generally imply other
changes, often to the inode; atime does not)
I'm still having problems.
The specific link that I'm looking at is
http://docs.sun.com/app/docs/doc/816-5175/6mbba7f4u?a=view
Which has, for example, a link to zoneadm(1M) with the address
http://docs.sun.com/app/docs/doc/REFMAN1M%20Version%205.0
Which gives the Error: The requested document
On Tue, Jun 20, 2006 at 02:18:34PM -0600, Gregory Shaw wrote:
Wouldn't that be:
5 seconds per write = 86400/5 = 17280 writes per day
256 rotated locations for 17280/256 = 67 writes per location per day
Resulting in (10/67) ~1492 days or 4.08 years before failure?
That's still a long
D'oh! Thanks for the tip.
I was testing the Solaris Express version, which is working fine, here:
http://docs.sun.com/app/docs/doc/819-2252/6n4i8rtv2?a=view
If you're working with OpenSolaris features, then the Solaris Express
docs will more closely correlate than the Solaris 10 man pages.
Richard Elling wrote:
Erik Trimble wrote:
Oh, and the newest thing in the consumer market is called hybrid
drives, which is a melding of a Flash drive with a Winchester
drive. It's originally targetted at the laptop market - think a 1GB
flash memory welded to a 40GB 2.5 hard drive in the
I'm looking into this and will send out an answer in
a day or two.
Lori Alt
Constantin Gonzalez wrote:
Hi,
I'm currently setting up a demo machine. It would be nice to set up everything
the way I like it, including a number of ZFS filesystems, then create a flash
archive, then install from
For my Google Summer of Code project for OpenSolaris, my job is to think about
new basic privileges. I like to propose five new basic privileges that relate
with file system access checks and may be used for daemons like ssh or
ssh-agent that (after starting up) never read or write user
Eric Schrock wrote:
On Tue, Jun 20, 2006 at 11:17:42AM -0700, Jonathan Adams wrote:
On Tue, Jun 20, 2006 at 09:32:58AM -0700, Richard Elling wrote:
Flash is (can be) a bit more sophisticated. The problem is that they
have a limited write endurance -- typically spec'ed at 100k writes to
any
Dana H. Myers wrote:
What I do not know yet is exactly how the flash portion of these hybrid
drives is administered. I rather expect that a non-hybrid-aware OS may
not actually exercise the flash storage on these drives by default; or
should I say, the flash storage will only be available to a
And, this is a worst case, no?
If the device itself also does some funky stuff under the covers, and
ZFS only writes an update if there is *actually* something to write,
then it could be much much longer than 4 years.
Actually - That's an interesting. I assume ZFS only writes something
when
I assume ZFS only writes something when there is actually data?
Right.
Jeff
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[EMAIL PROTECTED] wrote:
Also, options such as -nomtime and -noctime have been introduced
alongside -noatime in some free operating systems to limit the amount
of meta data that gets written back to disk.
Those seem rather pointless. (mtime and ctime generally imply other
changes,
24 matches
Mail list logo
