On 3/23/07, Milan Broz <[EMAIL PROTECTED]> wrote:
Disable barriers in dm-crypt because of current workqueue processing
can reorder requests.
--- linux-2.6.20.1.orig/drivers/md/dm-crypt.c 2007-03-23 15:07:11.0
+0100
+++ linux-2.6.20.1/drivers/md/dm-crypt.c2007-03-23
On 3/23/07, Milan Broz [EMAIL PROTECTED] wrote:
Disable barriers in dm-crypt because of current workqueue processing
can reorder requests.
--- linux-2.6.20.1.orig/drivers/md/dm-crypt.c 2007-03-23 15:07:11.0
+0100
+++ linux-2.6.20.1/drivers/md/dm-crypt.c2007-03-23
> Summary of what I've managed to rule out so far:
>1. this problem does not occur without dm-crypt
Please could you test attached patch ?
Sorry for another annoying reboot :-)
Milan
--
[EMAIL PROTECTED]
From: Milan Broz <[EMAIL PROTECTED]>
Disable barriers in dm-crypt because of current
Summary of what I've managed to rule out so far:
1. this problem does not occur without dm-crypt
Please could you test attached patch ?
Sorry for another annoying reboot :-)
Milan
--
[EMAIL PROTECTED]
From: Milan Broz [EMAIL PROTECTED]
Disable barriers in dm-crypt because of current
Summary of what I've managed to rule out so far:
1. this problem does not occur without dm-crypt
2. this problem does not occur when the file system hasn't been moved from
the SATA disk to USB
3. Both reiserfs and ext3 are affected by this problem, but ext3
merely slows down.
4. Unmounting and
On Wed, Mar 21, 2007 at 06:15:47PM +0200, Marti Raudsepp wrote:
> >On Tue, Mar 20, 2007 at 12:34:08PM +0200, Marti Raudsepp wrote:
> >lvmove
> >> wouldn't move the partition back to /dev/sda5 after "defragmenting" it.)
> However, when attempting to move back the LV, the allocater can create two
Marti Raudsepp wrote:
> This is a reproducible demonstration of the problem initially reported in my
> first e-mail, titled "PROBLEM: 'bio too big device' after moving to a USB
> disk" (http://lkml.org/lkml/2007/3/7/657)
...
> 06. Observe "bio too big device dm-0 (256 > 240)" messages in dmesg
>
Marti Raudsepp wrote:
This is a reproducible demonstration of the problem initially reported in my
first e-mail, titled PROBLEM: 'bio too big device' after moving to a USB
disk (http://lkml.org/lkml/2007/3/7/657)
...
06. Observe bio too big device dm-0 (256 240) messages in dmesg
[non]#
On Wed, Mar 21, 2007 at 06:15:47PM +0200, Marti Raudsepp wrote:
On Tue, Mar 20, 2007 at 12:34:08PM +0200, Marti Raudsepp wrote:
lvmove
wouldn't move the partition back to /dev/sda5 after defragmenting it.)
However, when attempting to move back the LV, the allocater can create two
extents,
Summary of what I've managed to rule out so far:
1. this problem does not occur without dm-crypt
2. this problem does not occur when the file system hasn't been moved from
the SATA disk to USB
3. Both reiserfs and ext3 are affected by this problem, but ext3
merely slows down.
4. Unmounting and
On 3/21/07, Lennart Sorensen <[EMAIL PROTECTED]> wrote:
Not that I really have a clue, but some questions anyhow:
Thanks for your response; I will answer the remaining questions after I've
freed up some space on the USB disk and done some additional tests. Possibly
later today, or maybe
On Tue, Mar 20, 2007 at 12:34:08PM +0200, Marti Raudsepp wrote:
> Second repost of "BUG: Killing and reviving files with USB disks", this time
> also destined to linux-fsdevel.
>
> This is a reproducible demonstration of the problem initially reported in my
> first e-mail, titled "PROBLEM: 'bio
On Tue, Mar 20, 2007 at 12:34:08PM +0200, Marti Raudsepp wrote:
Second repost of BUG: Killing and reviving files with USB disks, this time
also destined to linux-fsdevel.
This is a reproducible demonstration of the problem initially reported in my
first e-mail, titled PROBLEM: 'bio too big
On 3/21/07, Lennart Sorensen [EMAIL PROTECTED] wrote:
Not that I really have a clue, but some questions anyhow:
Thanks for your response; I will answer the remaining questions after I've
freed up some space on the USB disk and done some additional tests. Possibly
later today, or maybe tomorrow.
Hello LKML,
Second repost of "BUG: Killing and reviving files with USB disks", this time
also destined to linux-fsdevel.
This is a reproducible demonstration of the problem initially reported in my
first e-mail, titled "PROBLEM: 'bio too big device' after moving to a USB
disk"
15 matches
Mail list logo