On Mon, Aug 06, 2007 at 03:11:26PM +0100, Robert Milkowski wrote:
Hello Ed,
Thursday, June 14, 2007, 2:42:26 AM, you wrote:
ER On Wed, Jun 13, 2007 at 05:27:18PM -0700, Matthew Ahrens wrote:
To summarize my understanding of this issue: st_size on directories is
undefined; apps/libs
Not specifically a ZFS question, but is anyone monitoring disk space of
their ZFS filesystems via the Solaris 10 snmpd? I can't find any
64-bit counters in the MIB for disk space, so the normal tools I use
get completely wrong numbers for my 1-terabyte pool.
Looking over the info at
http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide#ZFS_and_NFS_Server_Performance
I see this:
Do not mix NFS legacy shared ZFS file systems and ZFS NFS shared file
systems. Go with ZFS NFS shared file systems.
Other than which command
My shop recently switched our mail fileserver from an old Network
Appliance to a Solaris box running ZFS. Customers are mostly
indifferent to the change, except for one or two uses which are
dramatically slower. The most noticeable problem is that deleting
email messages is much slower.
Each
On Fri, Jun 15, 2007 at 12:27:15AM +0200, Joerg Schilling wrote:
Bill Sommerfeld [EMAIL PROTECTED] wrote:
On Thu, 2007-06-14 at 09:09 +0200, [EMAIL PROTECTED] wrote:
The implication of which, of course, is that any app build for Solaris 9
or before which uses scandir may have picked up
On Wed, Jun 13, 2007 at 05:27:18PM -0700, Matthew Ahrens wrote:
To summarize my understanding of this issue: st_size on directories is
undefined; apps/libs which do anything other than display it are broken.
However, we should avoid exercising this bug in these broken apps if
possible.
On Wed, Jun 13, 2007 at 09:42:26PM -0400, Ed Ravin wrote:
As mentioned before, NetBSD's scandir(3) implementation was one. The
NetBSD project has fixed this in their CVS. OpenBSD and FreeBSD's scandir()
looks like another, I'll have to drop them a line.
I heard from an OpenBSD developer who
On Mon, Jun 11, 2007 at 02:03:58PM -0700, David Bustos wrote:
Quoth Ed Ravin on Thu, Jun 07, 2007 at 09:57:52PM -0700:
My Solaris 10 box is exporting a ZFS filesystem over NFS. I'm
accessing the data with a NetBSD 3.1 client, which only supports NFS
3. Everything works except when I look
Why does ZFS report such small directory sizes? For example, take a maildir
directory with ten entries:
total 2385
drwx-- 8 17121vmail 10 Jun 8 23:50 .
drwx--x--x 14 root root 14 May 12 2006 ..
drwx-- 5 17121vmail 5 May 25 18:16 .Trash
Oh, I see, this is bug 6479267: st_size (struct stat) is unreliable in ZFS.
Any word on when the fix will be out?
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
On Sat, Jun 09, 2007 at 10:16:34PM +0200, [EMAIL PROTECTED] wrote:
Oh, I see, this is bug 6479267: st_size (struct stat) is unreliable in
ZFS. Any word on when the fix will be out?
It's a bug in scandir (obviously) and it is filed as such.
Does scandir fail on zfs because of this or does
On Sat, Jun 09, 2007 at 02:01:35PM -0700, Eric Schrock wrote:
On Sat, Jun 09, 2007 at 01:56:35PM -0700, Ed Ravin wrote:
I encountered the problem in NetBSD's scandir(), when reading off
a Solaris NFS fileserver with ZFS filesystems. I've already filed a
bug report with NetBSD
My Solaris 10 box is exporting a ZFS filesystem over NFS. I'm accessing the
data with a NetBSD 3.1 client, which only supports NFS 3. Everything works
except when I look at the .zfs/snapshot directory. The first time I list out
the .zfs/snapshot directory, I get a correct listing of the
13 matches
Mail list logo
