From: Andreas Dilger <adilger@sun.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
cmm@us.ibm.com, tytso@mit.edu, sandeen@redhat.com,
akpm@linux-foundation.org, hch@infradead.org, steve@chygwyn.com,
npiggin@suse.de, mpatocka@redhat.com, linux-mm@kvack.org,
inux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH updated] ext4: Fix file fragmentation during large file write.
Date: Wed, 15 Oct 2008 20:44:07 -0600 [thread overview]
Message-ID: <20081016024407.GI2009@webber.adilger.int> (raw)
In-Reply-To: <1224114692.6938.48.camel@think.oraclecorp.com>
On Oct 15, 2008 19:51 -0400, Chris Mason wrote:
> Just FYI, I ran this with compilebench -i 20 --makej and my log is full
> of these:
>
> ext4_da_writepages: jbd2_start: 1024 pages, ino 520417; err -30
> Pid: 4072, comm: pdflush Not tainted 2.6.27 #2
-30 is -EROFS... Was the filesystem remounted read-only because of
an error?
> Call Trace:
> [<ffffffffa0048493>] ext4_da_writepages+0x171/0x2d3 [ext4]
> [<ffffffff802336be>] ? pick_next_task_fair+0x80/0x91
> [<ffffffff80228fa8>] ? source_load+0x2a/0x58
> [<ffffffff8038e499>] ? __next_cpu+0x19/0x26
> [<ffffffff8026748f>] do_writepages+0x28/0x37
> [<ffffffff802a6b39>] __writeback_single_inode+0x14f/0x26d
> [<ffffffff802a6fb7>] generic_sync_sb_inodes+0x1c1/0x2a2
> [<ffffffff802a70a1>] sync_sb_inodes+0x9/0xb
> [<ffffffff802a73dc>] writeback_inodes+0x64/0xad
> [<ffffffff802675db>] wb_kupdate+0x9a/0x10c
> [<ffffffff80267fd1>] ? pdflush+0x0/0x1e9
> [<ffffffff80267fd1>] ? pdflush+0x0/0x1e9
> [<ffffffff8026810e>] pdflush+0x13d/0x1e9
> [<ffffffff80267541>] ? wb_kupdate+0x0/0x10c
> [<ffffffff80248222>] kthread+0x49/0x77
> [<ffffffff8020c5e9>] child_rip+0xa/0x11
> [<ffffffff802481d9>] ? kthread+0x0/0x77
> [<ffffffff8020c5df>] ? child_rip+0x0/0x11
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-10-16 2:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 18:02 Aneesh Kumar K.V
2008-10-10 18:12 ` Aneesh Kumar K.V
2008-10-10 18:12 ` Aneesh Kumar K.V
2008-10-10 19:15 ` Chris Mason
2008-10-11 10:51 ` Nick Piggin
2008-10-11 18:14 ` Aneesh Kumar K.V
2008-10-11 19:07 ` Aneesh Kumar K.V
2008-10-15 20:41 ` Chris Mason
2008-10-15 23:51 ` Chris Mason
2008-10-16 2:41 ` Theodore Tso
2008-10-16 2:44 ` Andreas Dilger [this message]
2008-10-16 7:50 ` Aneesh Kumar K.V
2008-10-16 9:10 ` Aneesh Kumar K.V
2008-10-16 11:13 ` Aneesh Kumar K.V
-- strict thread matches above, loose matches on Subject: below --
2008-10-10 18:02 Aneesh Kumar K.V
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=20081016024407.GI2009@webber.adilger.int \
--to=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=hch@infradead.org \
--cc=inux-fsdevel@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpatocka@redhat.com \
--cc=npiggin@suse.de \
--cc=sandeen@redhat.com \
--cc=steve@chygwyn.com \
--cc=tytso@mit.edu \
/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