=
__ttl = 0x1
__tod = 0x498d189f 0x29fe4ddf
Leonid
-Original Message-
From: cindy.swearin...@sun.com [mailto:cindy.swearin...@sun.com]
Sent: Tuesday, February 10, 2009 3:42 PM
To: Roodnitsky, Leonid
Cc: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] ZFS corruption
Leonid,
You could use the fmdump -eV command to look for problems with these
disks. This command might generate a lot of output, but it should be
clear if the root cause is a problem accessing these devices.
I would also check /var/adm/messages for any driver-related messages.
Cindy
Leonid Roo
Dear All,
Is there any way to figure out which piece is at fault? Sun SAS RAID
(Adaptec/Intel) controller is reporting that drives are good, but ZFS is not
happy about checksum errors. Is there any way to figure out which component
introduced the error?
Leonid
--
This message posted from open
Leonid Roodnitsky wrote:
> Dear All,
>
> I am receiving DEGRAGED for zpool status -v. 3 out of 14 disks are reported
> as degraded with 'too many errors'. This is Build 99 running on x4240 with
> STK SAS RAID controller. Version of AAC driver is 2.2.5. I am not sure even
> where to start. Any ad
Dear All,
I am receiving DEGRAGED for zpool status -v. 3 out of 14 disks are reported as
degraded with 'too many errors'. This is Build 99 running on x4240 with STK SAS
RAID controller. Version of AAC driver is 2.2.5. I am not sure even where to
start. Any advice is very much appreciated. Tryin
If there was no redundancy configured in zfs then you're mostly toast. RAID is
no protection against data errors as has been told by zfs guys and you just
discovered.
I think your only option is to somehow setup a recent build of OpenSolaris
(05/08 or SXCE), configure it to not panic on checksu
Hi all,
It would appear that I have a zpool corruption issue to deal with...
pool is exported, but upon trying to import it, server panics. Are
there any tools available on a zpool that is in an exported state?
I've got a separate test bed in which I'm trying to recreate, but I
keep getting
Ed Saipetch wrote:
> To answer a number of questions:
>
> Regarding different controllers, I've tried 2 Syba Sil 3114 controllers
> purchased about 4 months apart. I've tried 5.4.3 firmware with one and
> 5.4.13 with another. Maybe Syba makes crappy Sil 3114 cards but it's the
> same one that
Mario,
I don't have any issues getting a new card. The root of the discussion
started because people did indeed post that they had good luck with
them. In fact, when I went out there and google'd to find which cards
would worked well, it seemed to be at the top of the list. I'm
interested t
I haven't seen the beginning of this discussion, but seeing SiI sets the
fire alarm off here.
The Silicon Image chipsets are renowned to be crap and causing data
corruption. At least the variants that usually go onto mainboards. Based
on this, I suggest that you should get a different card.
-mg
Nigel,
Thanks for the response! Basically my last method of testing was to
sftp a few 50-100MB files to /tank over a couple of minutes and force a
scrub after. The very first time this happened, I was using it as a NAS
device dumping data to it for over a week. I went to a customer's site
t
Ok, this is a strange problem!
You seem to have tried & eliminated all the possible issues
that the community has suggested!
I was hoping you would see some errors logged in
'/var/adm/messages' that would give a clue.
Your original 'zpool status' said 140 errors.
Over what time period are these o
Hi,
I have the same sil3114 based controller, installed in a dual Opteron box. I
have installed Solaris x86 and have had no problem with it, however I hardly
used that box with Solaris as my installation was only to try out Solaris on my
Opteron worksation. Instead, on that workstation I consta
Tried that... completely different cases with different power supplies.
On Oct 30, 2007, at 10:28 AM, Al Hopper wrote:
> On Mon, 29 Oct 2007, MC wrote:
>
>>> Here's what I've done so far:
>>
>> The obvious thing to test is the drive controller, so maybe you
>> should do that :)
>>
>
> Also - wh
On Mon, 29 Oct 2007, MC wrote:
>> Here's what I've done so far:
>
> The obvious thing to test is the drive controller, so maybe you should do
> that :)
>
Also - while you're doing swapTronics - don't forget the Power Supply
(PSU). Ensure that your PSU has sufficient capacity on its 12Volt
rai
To answer a number of questions:
Regarding different controllers, I've tried 2 Syba Sil 3114 controllers
purchased about 4 months apart. I've tried 5.4.3 firmware with one and 5.4.13
with another. Maybe Syba makes crappy Sil 3114 cards but it's the same one
that someone on blogs.sun.com used
On Tue, 30 Oct 2007, Tomasz Torcz wrote:
> On 10/30/07, Neal Pollack <[EMAIL PROTECTED]> wrote:
>>> I'm experiencing major checksum errors when using a syba silicon image 3114
>>> based pci sata controller w/ nonraid firmware. I've tested by copying data
>>> via sftp and smb. With everything I
One thing to check before you blame your controller:
Are the SATA cables close together for an extended length?
Basically, most SATA cables will generate massive levels of cross-talk between
them if they're tied together or a run parallel in close proximity for a part
of
their run-leng
On 10/30/07, Neal Pollack <[EMAIL PROTECTED]> wrote:
> > I'm experiencing major checksum errors when using a syba silicon image 3114
> > based pci sata controller w/ nonraid firmware. I've tested by copying data
> > via sftp and smb. With everything I've swapped out, I can't fathom this
> > be
And are you seeing any error messages in '/var/adm/messages'
indicating any failure on the disk controller card?
If so, please post a sample back here to the forum.
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@open
First off, can we just confirm the exact version of the Silicon Image Card
and which driver Solaris is using.
Use 'prtconf -pv' and '/usr/X11/bin/scanpci'
to get the PCI vendor & device ID information.
Use 'prtconf -D' to confirm which drivers are being used by which devices.
And 'modinfo' will
Edward Saipetch wrote:
> Neal Pollack wrote:
>> Ed Saipetch wrote:
>>> Hello,
>>>
>>> I'm experiencing major checksum errors when using a syba silicon
>>> image 3114 based pci sata controller w/ nonraid firmware. I've
>>> tested by copying data via sftp and smb. With everything I've
>>> swappe
Will Murnane wrote:
> On 10/30/07, Edward Saipetch <[EMAIL PROTECTED]> wrote:
>> As a side note, what SATA cards are people having luck with?
> Running b74, I'm very happy with the Marvell mv88sx6081-based Supermicro card:
> http://www.supermicro.com/products/accessories/addon/AoC-SAT2-MV8.cfm
> ht
On 10/30/07, Edward Saipetch <[EMAIL PROTECTED]> wrote:
> As a side note, what SATA cards are people having luck with?
Running b74, I'm very happy with the Marvell mv88sx6081-based Supermicro card:
http://www.supermicro.com/products/accessories/addon/AoC-SAT2-MV8.cfm
http://www.newegg.com/Product/P
> Here's what I've done so far:
The obvious thing to test is the drive controller, so maybe you should do that
:)
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/l
Neal Pollack wrote:
> Ed Saipetch wrote:
>> Hello,
>>
>> I'm experiencing major checksum errors when using a syba silicon
>> image 3114 based pci sata controller w/ nonraid firmware. I've
>> tested by copying data via sftp and smb. With everything I've
>> swapped out, I can't fathom this be
Ed Saipetch wrote:
> Hello,
>
> I'm experiencing major checksum errors when using a syba silicon image 3114
> based pci sata controller w/ nonraid firmware. I've tested by copying data
> via sftp and smb. With everything I've swapped out, I can't fathom this
> being a hardware problem.
I ca
You have not mentioned if you have swapped the 3114 based HBA itself...?
Have you tried a different HBA? :)
Nathan.
Ed Saipetch wrote:
> Hello,
>
> I'm experiencing major checksum errors when using a syba silicon image 3114
> based pci sata controller w/ nonraid firmware. I've tested by copyi
Hello,
I'm experiencing major checksum errors when using a syba silicon image 3114
based pci sata controller w/ nonraid firmware. I've tested by copying data via
sftp and smb. With everything I've swapped out, I can't fathom this being a
hardware problem. There have been quite a few blog pos
On 2/11/07, Jeff Bonwick <[EMAIL PROTECTED]> wrote:
The object number is in hex. 21e282 hex is 2220674 decimal --
give that a whirl.
This is all better now thanks to some recent work by Eric Kustarz:
6410433 'zpool status -v' would be more useful with filenames
This was integrated into Nevada
Hi Joe,
Joe Little wrote:
So, I attempting to find the inode from the result of a "zpool status -v":
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
cc 21e382 lvl=0 blkid=0
>
Well, 21e282 appears to not be a valid number for "find .
On 10 February, 2007 - Joe Little sent me these 0,4K bytes:
> So, I attempting to find the inode from the result of a "zpool status -v":
>
> errors: The following persistent errors have been detected:
>
> DATASET OBJECT RANGE
> cc 21e382 lvl=0 blkid=0
>
>
> Well, 21e
The object number is in hex. 21e282 hex is 2220674 decimal --
give that a whirl.
This is all better now thanks to some recent work by Eric Kustarz:
6410433 'zpool status -v' would be more useful with filenames
This was integrated into Nevada build 57.
Jeff
On Sat, Feb 10, 2007 at 05:18:05PM -
So, I attempting to find the inode from the result of a "zpool status -v":
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
cc 21e382 lvl=0 blkid=0
Well, 21e282 appears to not be a valid number for "find . -inum blah"
Any suggestions?
Bill Casale wrote:
Please reply directly to me. Seeing the message below.
Is it possible to determine exactly which file is corrupted?
I was thinking the OBJECT/RANGE info may be pointing to it
but I don't know how to equate that to a file.
This is bug:
6410433 'zpool status -v' would be more
Bill,
If you want to find the file associated with the corruption you could do
a "find /u01 -inum 4741362" or use the output of "zdb -d u01" to
find the object associated with that id.
Thanks,
George
Bill Casale wrote:
Please reply directly to me. Seeing the message below.
Is it possib
Hello Bill,
Tuesday, December 12, 2006, 2:34:01 PM, you wrote:
BC> Please reply directly to me. Seeing the message below.
BC> Is it possible to determine exactly which file is corrupted?
BC> I was thinking the OBJECT/RANGE info may be pointing to it
BC> but I don't know how to equate that to a f
Please reply directly to me. Seeing the message below.
Is it possible to determine exactly which file is corrupted?
I was thinking the OBJECT/RANGE info may be pointing to it
but I don't know how to equate that to a file.
# zpool status -v
pool: u01
state: ONLINE
status: One or more devices
38 matches
Mail list logo
