All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Dušan Čolić" <dusanc@gmail.com>
Cc: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: [xfstests/generic/081] Kernel panic with reg40 plugin and R4-for-4.1.5.patch
Date: Thu, 10 Sep 2015 22:10:49 +0200	[thread overview]
Message-ID: <55F1E3C9.5080109@gmail.com> (raw)
In-Reply-To: <CADW=+3mQjNcwFzaWNdXDG+-_We=mQ+_1EfbS_Jy9KkiFx5Bi=w@mail.gmail.com>



On 09/10/2015 09:42 PM, Dušan Čolić wrote:
> On Thu, Sep 10, 2015 at 9:20 PM, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>> Actually, this is not a regression.
>> The attached patch prevents the panic.
>> By default on IO errors reiser4 partition will be remounted as "readonly".
>>
>> No ideas why accessing /dev/dm-X causes IO error.
>> Reiser4 is not the culprit ;) You can narrow down this, if interesting.
>> I think that something is wrong with LVM settings...
>>
> I looked more into this: This test fills up dm snapshot (writes 5MB to
> 4MB snapshot) so we get IO error because it's full.


IO error because of no space - it is very strange,
especially when reading the device (as in my case):

# dd if=/dev/dm-3 of=/dev/null bs=4096 count=1


>   It doesn't trigger
> on ccreg40 because ccreg40 compresses data so 5MB of compressible data
> < 4MB space ;)
> xfstests uses compressible data for disk full tests so on ccreg40 they
> give false positive. Are ccreg40 and reg40 code paths for disk full
> situation the same?
> I'll look into fixing xfstetsts.
>> Thanks,
>> Edward.
>>
>>
>>
>> On 09/04/2015 09:35 AM, Dušan Čolić wrote:
>>> Kernel: 4.1.6
>>> R4 patch: 4.1.5
>>> Test: xfstests/generic/081 "Test I/O error path by fully filling an dm
>>> snapshot."
>>>
>>> Test passes cleanly with ccreg40 but kernel panics with reg40 plugin.
>>> Picture of the panic, as I had no other means of capturing it, is in
>>> attachment.
>>>
>>> xfstests local.config section:
>>>
>>> [r4Hybrid]
>>> MKFS_OPTIONS="-o create=reg40"
>>> MOUNT_OPTIONS="-o noatime"
>>>
>>> Have a nice day.
>>>
>>> Dushan
>>

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-09-10 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADW=+3=x+ajq+N4QqwmRQ-4uEAPEpr5xopV+31zz2HQonMc_UA@mail.gmail.com>
2015-09-10 19:20 ` [xfstests/generic/081] Kernel panic with reg40 plugin and R4-for-4.1.5.patch Edward Shishkin
2015-09-10 19:42   ` Dušan Čolić
2015-09-10 20:10     ` Edward Shishkin [this message]
2015-09-10 20:21       ` Dušan Čolić
2015-09-10 20:47         ` Edward Shishkin
2015-09-10 20:24       ` Edward Shishkin

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=55F1E3C9.5080109@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=dusanc@gmail.com \
    --cc=reiserfs-devel@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.