On Apr 27, 2008, at 4:39 PM, Carson Gaspar wrote:
> Ian Collins wrote:
>> Carson Gaspar wrote:
>
>>> If this is possible, it's entirely undocumented... Actually, fmd's
>>> documentation is generally terrible. The sum total of configuration
>>> information is:
>>>
>>> FILES
>>> /etc/fm/fmd
http://www.sun.com/bigadmin/features/articles/selfheal.jsp
-- mark
Carson Gaspar wrote:
Ian Collins wrote:
Carson Gaspar wrote:
If this is possible, it's entirely undocumented... Actually, fmd's
documentation is generally terrible. The sum total of configuration
information is:
Ian Collins wrote:
> Carson Gaspar wrote:
>> If this is possible, it's entirely undocumented... Actually, fmd's
>> documentation is generally terrible. The sum total of configuration
>> information is:
>>
>> FILES
>> /etc/fm/fmd Fault manager configuration direc-
>>
Carson Gaspar wrote:
> Nathan Kroenert - Server ESG wrote:
>
>
>> I also *believe* (though am not certain - Perhaps someone else on the
>> list might be?) it would be possible to have each *event* (so - the
>> individual events that lead to a Fault Diagnosis) generate a message if
>> it was r
Nathan Kroenert - Server ESG wrote:
> I also *believe* (though am not certain - Perhaps someone else on the
> list might be?) it would be possible to have each *event* (so - the
> individual events that lead to a Fault Diagnosis) generate a message if
> it was required, though I have never take
Note: IANATZD (I Am Not A Team-ZFS Dude)
Speaking as a Hardware Guy, knowing that something is happening, has
happened or is indicated to happen is a Good Thing (tm).
Begin unlikely, but possible scenario:
If, for instance, I'm getting a cluster of read errors (or, perhaps bad
blocks), I could
On Sat, 26 Apr 2008, Carson Gaspar wrote:
>> It's not safe to jump to this conclusion. Disk drivers that support FMA
>> won't log error messages to /var/adm/messages. As more support for I/O
>> FMA shows up, you won't see random spew in the messages file any more.
>
>
> That is a Very Bad Idea.
fmd(1M) can log faults to syslogd that are already diagnosed. Why
would you want the random spew as well?
-- mark
Carson Gaspar wrote:
[EMAIL PROTECTED] wrote:
It's not safe to jump to this conclusion. Disk drivers that support FMA
won't log error messages to /var/adm/messages. As more s
[EMAIL PROTECTED] wrote:
> It's not safe to jump to this conclusion. Disk drivers that support FMA
> won't log error messages to /var/adm/messages. As more support for I/O
> FMA shows up, you won't see random spew in the messages file any more.
That is a Very Bad Idea. Please convey this to wh
> I'm just interested in understanding how zfs determined there was data
> corruption when I have checksums disabled and there were no
> non-retryable read errors reported in the messages file.
If the metadata is corrupt, how is ZFS going to find the data blocks on
disk?
> > I don't believe it w
Just to clarify this post. This isn't data I care about recovering.
I'm just interested in understanding how zfs determined there was data
corruption when I have checksums disabled and there were no
non-retryable read errors reported in the messages file.
On Wed, Apr 23, 2008 at 9:52 PM, Victor En
Thanks! That would explain things. I don't believe it was a real disk
read error because of the absence of evidence in /var/adm/messages.
I'll review the man page and documentation to confirm that metadata is
checksummed.
Regards,
Vic
On Wed, Apr 23, 2008 at 6:30 PM, Nathan Kroenert
<[EMAIL PRO
> Since no specific file or directory is mentioned
install newer bits and get better info automatically
but for now type:
zdb -vvv zpool1 17
zdb -vvv zpool1 18
zdb -vvv zpool1 19
echo remove those objects
zpool clear zpool1
zpool scrub zpool1
___
zfs-d
I'm just taking a stab here, so could be completely wrong, but IIRC,
even if you disable checksum, it still checksums the metadata...
So, it could be metadata checksum errors.
Others on the list might have some funky zdb thingies you could to see
what it actually is...
Note: typed pre caffeine
I'm hoping someone can help me understand a zfs data corruption symptom. We
have a zpool with checksum turned off. Zpool status shows that data corruption
occured. The application using the pool at the time reported a "read" error and
zoppl status (see below) shows 2 read errors on a device. The
15 matches
Mail list logo
