Re: PROBLEM: write to jbod with 3TB and 160GB drives hits BUG/oops

[NeilBrown <neilb@suse.de>]

[-- Attachment #1: Type: text/plain, Size: 971 bytes --]

On Thu, 23 Apr 2015 16:46:42 -0700 Charles Bertsch <cbertsch@cox.net> wrote:

> 1.  PROBLEM: write to jbod with 3TB and 160GB drives hits BUG/oops
> 
> 2.  Description.  Using linux-3.18.5, linux-3.18.7, and linux-4.0 a 
> two-drive jbod created using one 3TB drive and one 160GB drive will 
> SOMETIMES hit a BUG call at linux-4.0/fs/buffer.c:3220

By "jbod" I assume you mean "linear array".

You say this happens without any filesystem on the array, yet the stack
traces clearly show ext2 in use.
Maybe some weird interaction is happening between the the filesystem and the
linear array.
But please confirm that the stack trace happened when there was no filesystem
on the array you were testing, and report what filesystems you do have which
use ext2.

Is there any chance you could use "git bisect" to find out exactly which
commit introduced the problem?  That is the mostly likely path to a solution.

Thanks for the report,

NeilBrown



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]