From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of James
I’m trying to select the appropriate disk spindle speed for a proposal and
would welcome any experience and opinions (e.g. has anyone actively
chosen 10k/15k drives for a new ZFS
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Roy Sigurd Karlsbakk
Dedup is *hungry* for RAM. 8GB is not enough for your configuration,
most likely! First guess: double the RAM and then you might have
better
luck.
I know...
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Roy Sigurd Karlsbakk
Sorry about the initial post - it was wrong. The hardware configuration was
right, but for initial tests, I use NFS, meaning sync writes. This obviously
stresses the
On 01/31/11 01:09 PM, Pasi Kärkkäinen wrote:
On Mon, Jan 31, 2011 at 03:41:52PM +0100, Joerg Schilling wrote:
Brandon Highbh...@freaks.com wrote:
On Sat, Jan 29, 2011 at 8:31 AM, Edward Ned Harvey
opensolarisisdeadlongliveopensola...@nedharvey.com wrote:
What is the
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Roy Sigurd Karlsbakk
Even *with* an L2ARC, your memory requirements are *substantial*,
because the L2ARC itself needs RAM. 8 GB is simply inadequate for your
test.
With 50TB storage,
On 1/31/2011 4:19 PM, Mike Tancsa wrote:
On 1/31/2011 3:14 PM, Cindy Swearingen wrote:
Hi Mike,
Yes, this is looking much better.
Some combination of removing corrupted files indicated in the zpool
status -v output, running zpool scrub and then zpool clear should
resolve the corruption,
Dedup is *hungry* for RAM. 8GB is not enough for
your configuration,
most likely! First guess: double the RAM and then
you might have
better
luck.
I know... that's why I use L2ARC
What is zdb -D showing?
Does this give you any clue;
Excellent.
I think you are good for now as long as your hardware setup is stable.
You survived a severe hardware failure so say a prayer and make sure
this doesn't happen again. Always have good backups.
Thanks,
Cindy
On 02/01/11 06:56, Mike Tancsa wrote:
On 1/31/2011 4:19 PM, Mike Tancsa
I recently discovered a drive failure (either that or a loose cable, I
need to investigate further) on my home fileserver. 'fmadm faulty'
returns no output, but I can clearly see a failure when I do zpool
status -v:
pool: tank
state: DEGRADED
status: One or more devices has been removed by the
Hi Krunal,
It looks to me like FMA thinks that you removed the disk so you'll need
to confirm whether the cable dropped or something else.
I agree that we need to get email updates for failing devices.
See if fmdump generated an error report using the commands below.
Thanks,
Cindy
# fmdump
Hello All,
I have two questions related to zfs snapshot -r
1. When zfs snapshot -r tank@today command is issued, does it creates
snapshots for all the descendent file systems at the same moment? I mean to
say if the command is issued at 10:20:35 PM, does the creation time of all
the snapshots
On Tue, Feb 1, 2011 at 1:29 PM, Cindy Swearingen
cindy.swearin...@oracle.com wrote:
I agree that we need to get email updates for failing devices.
Definitely!
See if fmdump generated an error report using the commands below.
Unfortunately not, see below:
movax@megatron:/root# fmdump
TIME
I misspoke and should clarify:
1. fmdump identifies fault reports that explain system issues
2. fmdump -eV identifies errors or problem symptoms
I'm unclear about your REMOVED status. I don't see it very often.
The ZFS Admin Guide says:
REMOVED
The device was physically removed while the
On Tue, Feb 1 at 10:54, Rahul Deb wrote:
Hello All,
I have two questions related to zfs snapshot -r
1. When zfs snapshot -r tank@today command is issued, does it creates
snapshots for all the�descendent file systems at the same moment? I mean
to say if the command is issued at
On Tue, Feb 1, 2011 at 6:11 PM, Cindy Swearingen
cindy.swearin...@oracle.com wrote:
I misspoke and should clarify:
1. fmdump identifies fault reports that explain system issues
2. fmdump -eV identifies errors or problem symptoms
Gotcha; fmdump -eV gives me the information I need. It appears
On Feb 1, 2011, at 5:56 AM, Mike Tancsa wrote:
On 1/31/2011 4:19 PM, Mike Tancsa wrote:
On 1/31/2011 3:14 PM, Cindy Swearingen wrote:
Hi Mike,
Yes, this is looking much better.
Some combination of removing corrupted files indicated in the zpool
status -v output, running zpool scrub and
On Feb 1, 2011, at 5:52 PM, Krunal Desai wrote:
On Tue, Feb 1, 2011 at 6:11 PM, Cindy Swearingen
cindy.swearin...@oracle.com wrote:
I misspoke and should clarify:
1. fmdump identifies fault reports that explain system issues
2. fmdump -eV identifies errors or problem symptoms
Gotcha;
The output of fmdump is explicit. I am interested to know if you saw
aborts and timeouts or some other errors.
I have the machine off atm while I install new disks (18x ST32000542AS), but
IIRC they appeared as transport errors (scsi.something.transport, I can paste
the exact errors in a
On Feb 1, 2011, at 6:49 PM, Krunal Desai wrote:
The output of fmdump is explicit. I am interested to know if you saw
aborts and timeouts or some other errors.
I have the machine off atm while I install new disks (18x ST32000542AS), but
IIRC they appeared as transport errors
On Tue, Feb 1, 2011 at 11:34 PM, Richard Elling
richard.ell...@gmail.com wrote:
There is a failure going on here. It could be a cable or it could be a bad
disk or firmware. The actual fault might not be in the disk reporting the
errors (!)
It is not a media error.
Errors were as follows:
20 matches
Mail list logo
