All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lord <lord@xfs.org>
To: Torben Viets <Viets@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS dm_crypt BUG?
Date: Sun, 27 Feb 2005 13:34:31 -0600	[thread overview]
Message-ID: <422220C7.8090001@xfs.org> (raw)
In-Reply-To: <422214D6.2000206@web.de>

Torben Viets wrote:
> Hello,
> 
> I have a problem with the XFS-filesystem, I use the Kernel 2.6.10 and 
> 2.6.11-rc4 and rc5 everytime the same behavior.
> 
> I have a RAID 5(md0) with 3 disks on md0 (chunk-size 128) there is a 
> logical volume (/dev/data/mp3-crypt) which is crypted with AES and the 
> encrypted version ist under /dev/mapper/mp3, if the filestem on it is 
> xfs and then copie some files on it then I get a kernel panic, mostly on 
> greater files (>200MB), if I make the same thing with ext3 there is no 
> problem. My first thougt was that the problem is that I make a snapshot 
> of the device, but if i remove this it won't work anyway.
> 
> My sytem is a Pentium4 1800Mhz
> 512 MB SDRAM
> 
> I can't show you the kernel panic message, because I didn't found it in 
> the syslog, it is only on the screen,
> 
> I'm not sure what infos you need too.
> 
> greetings
> Torben Viets
> 

The complete kernel panic is what is needed to get anywhere with this.

If all else fails, get a digital camera and take a picture of it,
although you may need to reconfigure your console to get enough lines
displayed. A console down a serial line to another computer is the best
way of capturing these though.

Just on a hunch, check if you have 4K stacks turned on, if you do, go
back to 8K stacks and see if that cures it.

Steve



  reply	other threads:[~2005-02-27 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 18:43 XFS dm_crypt BUG? Torben Viets
2005-02-27 19:34 ` Stephen Lord [this message]
2005-02-27 22:22   ` Nathan Scott
     [not found]     ` <422B6885.7090908@web.de>
     [not found]       ` <20050307080929.B2751595@wobbly.melbourne.sgi.com>
2005-03-13 14:24         ` Torben Viets

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=422220C7.8090001@xfs.org \
    --to=lord@xfs.org \
    --cc=Viets@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.