public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: nscott@aconex.com
Cc: "Jochen K." <jochen.f.k@googlemail.com>, xfs@oss.sgi.com
Subject: Re: Cant find sunit and swidth on luks encrypted raid6 device
Date: Wed, 19 Sep 2007 17:47:31 -0500	[thread overview]
Message-ID: <46F1A703.6040309@sandeen.net> (raw)
In-Reply-To: <33249.192.168.3.1.1190241583.squirrel@mail.aconex.com>

nscott@aconex.com wrote:
>> Eric Sandeen wrote:
>>
>> 2b2d4c133680: Badness in key lookup (length)
>> bp=(bno 13673620728, len 131072 bytes) key=(bno 13673620728, len 4096
>> bytes)
>>
>> If we take out the pwrite that does the end-of-device zeroing, we don't
>> get the error... but that's been there since forever, so again, I'm a
>> bit confused here.
> 
> libxfs has been changing alot - most likely the problem lies in the buffer
> caching
> code there - Barry will probably recognise the error (when he gets online).

--- xfs-cmds/xfsprogs/libxfs/rdwr.c	2007/02/21 14:37:52	1.34
+++ xfs-cmds/xfsprogs/libxfs/rdwr.c	2007/07/16 15:55:26	1.35
@@ -24,6 +24,8 @@
 #define BDSTRAT_SIZE	(256 * 1024)
 #define min(x, y)	((x) < (y) ? (x) : (y))

+#define IO_BCOMPARE_CHECK
+

Yep.... :)

-Eric

> cheers.
> 
> --
> Nathan
> 
> 

  reply	other threads:[~2007-09-19 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 18:29 Cant find sunit and swidth on luks encrypted raid6 device Jochen K.
2007-09-19 19:40 ` Bhagi rathi
2007-09-19 19:42 ` Eric Sandeen
2007-09-19 22:33   ` Eric Sandeen
2007-09-19 22:39     ` nscott
2007-09-19 22:47       ` Eric Sandeen [this message]
2007-09-19 22:50         ` Jochen K.
2007-09-19 22:56           ` Eric Sandeen
2007-09-20  0:54   ` Barry Naujok
2007-09-20  2:36   ` Barry Naujok

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46F1A703.6040309@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=jochen.f.k@googlemail.com \
    --cc=nscott@aconex.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox