From: Eric Sandeen <sandeen@redhat.com>
To: Gary Hawco <ghawco@cox.net>
Cc: Mingming <cmm@us.ibm.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Segmentation Faults with 062508 ext4-patch-queue snapshot
Date: Wed, 25 Jun 2008 23:14:10 -0500 [thread overview]
Message-ID: <48631792.3040202@redhat.com> (raw)
In-Reply-To: <3.0.6.32.20080625135340.02423ed8@pop.west.cox.net>
Gary Hawco wrote:
> I redid my tests on the last few ext-patch-queue snapshots.
>
> The snapshot:
> ext4-patch-queue-476b1104923c2228b48aee73070cddd5430b3b54.tar.gz from
> 062408 @2256hrs GMT works fine. No segfaults.
>
> The latest snapshot:
> ext4-patch-queue-b5db22ef52ed53d8e3fa978a5a29e1609c9333aa.tar.gz from
> 062508 @ 0019hrs GMT causes segmentation faults whenever I do extensive
> copying of small files (my Gentoo portage tree & metadata cache folders) to
> another ext4dev partition set up identically and then when I make a tarball
> from this copied data.
>
> I have been able to reproduce the segfaults consistently. Both partitions
> were formatted with flex_bg & meta_bg features enabled (obviously no
> resize_inodes) and are set for ordered data mode.
>
> I assume delalloc is enabled although ext4-patch-queue does not yet print
> message saying so on boot like mballoc does.
>
> Any suggestions would be most appreciated.
Do you get kernel messages when this happens? If so can you provide them?
Thanks,
-Eric
next prev parent reply other threads:[~2008-06-26 4:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 13:53 Segmentation Faults with 062508 ext4-patch-queue snapshot Gary Hawco
2008-06-26 4:14 ` Eric Sandeen [this message]
2008-06-26 22:12 ` Segmentation Faults with both 062608 snapshots Gary Hawco
2008-07-01 2:32 ` Theodore Tso
2008-07-01 0:00 ` More ext4dev snapshot weirdness Gary Hawco
2008-07-01 16:02 ` Theodore Tso
2008-07-01 10:54 ` delalloc filesystem corruption Gary Hawco
2008-07-01 23:00 ` Mingming Cao
2008-07-01 17:50 ` Gentoo with ext4-patch-queue snapshots Gary Hawco
2008-07-02 17:19 ` Mingming Cao
2008-07-02 20:33 ` Mingming Cao
2008-07-03 14:07 ` Aneesh Kumar
2008-07-03 17:38 ` Mingming Cao
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=48631792.3040202@redhat.com \
--to=sandeen@redhat.com \
--cc=cmm@us.ibm.com \
--cc=ghawco@cox.net \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).