public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Tsvetkov <alexander.tsvetkov@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandee <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: xfs_logprint segfault with external log
Date: Mon, 16 Feb 2015 16:55:14 +0300	[thread overview]
Message-ID: <54E1F6C2.4060105@oracle.com> (raw)
In-Reply-To: <20150212230940.GD12722@dastard>


On 02/13/2015 02:09 AM, Dave Chinner wrote:
> On Thu, Feb 12, 2015 at 02:52:45PM +0300, Alexander Tsvetkov wrote:
>> On 02/11/2015 11:54 PM, Dave Chinner wrote:
>>> On Wed, Feb 11, 2015 at 04:51:44PM +0300, Alexander Tsvetkov wrote:
>>>> Hello,
>>>>
>>>> I've obtained corrupted xfs log after some sanity xfs testing:
>>>>
>>>> "log=logfile
>>>> log_size=855
>>>>
>>>> dd if=/dev/zero "of=$log" bs=4096 count=$log_size
>>>> loopdev=$(losetup -f)
>>>> losetup $loopdev $log
>>>>
>>>> mkfs.xfs -f -m crc=1 -llogdev=$loopdev,size=${log_size}b $SCRATCH_DEV
>>>> mount -t xfs -ologdev=$loopdev $SCRATCH_DEV $SCRATCH_MNT
>>>> ./fdtree.sh  -l 4 -d 4 -C -o $SCRATCH_MNT
>>>> sync
>>>> umount $SCRATCH_MNT
>>>>
>>>> xfs_logprint -l $loopdev $SCRATCH_DEV"
>>>>
>>>> Test makes crc enabled xfs filesystem with the external log of
>>>> minimal allowed size and then creates on this fs the small directory
>>>> tree
>>>> with sub directories and files of fixed depth and size with help of
>>>> fdtree utility:
>>>> https://computing.llnl.gov/?set=code&page=sio_downloads
>>> Just take metadump image and put it somewhere we can down load it.
>>>
>>>> After that xfs_logprint stably reports bad data in log:
> Please try the patch below, it fixes the problem on the image you
> provided.

I've restored provided image to filesystem with the same log file, 
applied patch to latest xfsprogs and have stable pass runs
of xfs_logprint on that filesystem and running with xfsprogs without 
this patch results to xfs_logprint segfaults reported that means patch 
is working.
The problem that it is not working for repeated test runs where 
xfs_logprint still continue to report bad log data. It seems it is 
working for some
cases including this image, because sometimes test can be passed but 
most part of test runs have still this xfs_logprint log error. Here is 
another fs image
that is still failed for me with patch applied to xfsprogs: 
https://drive.google.com/file/d/0B1Cg0_B_ui2gM1Bzdkc3TWVqbGM/view?usp=sharing


> Cheers,
>
> Dave.
Thanks,
Alexander Tsvetkov

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-02-16 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 13:51 xfs_logprint segfault with external log Alexander Tsvetkov
2015-02-11 15:51 ` Eric Sandeen
2015-02-11 20:54 ` Dave Chinner
2015-02-12 11:52   ` Alexander Tsvetkov
2015-02-12 23:09     ` Dave Chinner
2015-02-16 13:55       ` Alexander Tsvetkov [this message]
2015-02-17  1:38         ` Dave Chinner
2015-02-17  9:26           ` Alexander Tsvetkov

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=54E1F6C2.4060105@oracle.com \
    --to=alexander.tsvetkov@oracle.com \
    --cc=david@fromorbit.com \
    --cc=sandeen@sandeen.net \
    --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