On Tue, May 31, 2011 at 11:25:56AM +0200, Olaf Seibert wrote:
> On Mon 30 May 2011 at 12:19:10 -0500, Dan Nelson wrote:
> > The ZFS compression code will panic if it can't allocate the buffer needed
> > to store the compressed data, so that's unlikely to be your problem. The
> > only time I have s
On Mon 30 May 2011 at 12:19:10 -0500, Dan Nelson wrote:
> The ZFS compression code will panic if it can't allocate the buffer needed
> to store the compressed data, so that's unlikely to be your problem. The
> only time I have seen an "illegal byte sequence" error was when trying to
> copy raw dis
Hi,
2011/5/30 Olaf Seibert
> "My" FreeBSD system somehow rebooted itself last friday in the early
> hours in the morning, and since then /var/log/messages is full with
> messages like these:
>
> May 30 10:38:28 fourquid root: ZFS: zpool I/O failure, zpool=tank error=86
> May 30 10:38:38 fourquid
- Original Message -
From: "Dan Nelson"
The zfs IO code overloads the EILSEQ error code and uses it as a "checksum
error" code. Returning that error for the same block on all disks is
definitely weird. Could you have run a partitioning tool, or some other
program that would have done
In the last episode (May 30), Olaf Seibert said:
> On Mon 30 May 2011 at 03:33:49 -0700, Jeremy Chadwick wrote:
> > On Mon, May 30, 2011 at 12:10:51PM +0200, Olaf Seibert wrote:
> > I'm not sure why this didn't actually map to a filename on the system
> > however. I've never quite understood what
On Mon 30 May 2011 at 03:33:49 -0700, Jeremy Chadwick wrote:
> On Mon, May 30, 2011 at 12:10:51PM +0200, Olaf Seibert wrote:
> I'm not sure why this didn't actually map to a filename on the system
> however. I've never quite understood what the hexadecimal values shown
> represent (I have ideas bu
On Mon, May 30, 2011 at 12:10:51PM +0200, Olaf Seibert wrote:
> On Mon 30 May 2011 at 11:35:46 +0200, Olaf Seibert wrote:
> > How do I identify which files it is listing here?
On Solaris anyway, "zpool status -v" is supposed to show this.
Occasionally it shows something like <0xXX>:, rather than a
On Mon 30 May 2011 at 11:35:46 +0200, Olaf Seibert wrote:
> How do I identify which files it is listing here?
The nighly 'find' has found the files for me. It is actually a bunch of
directories, that were likely in use when the crash occurred.
They give an "interesting" error when you try to ls t
