From: Andrew Morton <akpm@digeo.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: disk corruption in 2.5.66-bk5 - 2.5.69
Date: Thu, 15 May 2003 00:57:18 -0700 [thread overview]
Message-ID: <20030515005718.7cc41827.akpm@digeo.com> (raw)
In-Reply-To: <200305150258.h4F2wbR27255@freya.yggdrasil.com>
"Adam J. Richter" <adam@yggdrasil.com> wrote:
>
> linux-2.5.66-bk5 changed blkdev_put in fs/block_dev.c
> to only call sync_blockdev if bdev->bd_openers drops to zero.
> For me, this has resulted in disk corruption when lilo runs
> under kernels 2.5.66-bk5 through 2.5.69, even if I run
> "sync" repeatedly after running lilo.
Works OK here with a simple test:
sleep 10000 < /dev/hda5 &
cat < some-file > /dev/hda5
sync
<press reset>
cmp some-file /dev/hda5
LILO does a global sync itself before quitting. Check to see if there's a
lot of writeout happening. See if there's writeout happening when you run
sync manually.
Maybe take a copy of /dev/hda1 into a regular file, then reboot, then
compare with what's on the disk.
Check that /proc/meminfo:Dirty goes to zero after `sync'.
prev parent reply other threads:[~2003-05-15 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 2:58 Adam J. Richter
2003-05-15 7:57 ` Andrew Morton [this message]
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=20030515005718.7cc41827.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®