From: "Rogério Brito" <rbrito@ime.usp.br>
To: Theodore Tso <tytso@mit.edu>,
Alexandre Lymberopoulos <lymber@gmail.com>,
502583@bugs.debian.org, 502583-submitter@bugs.debian.org,
linux-kernel@vger.kernel.org, rafael@debian.org
Subject: Re: Bug#502583: scary messages in dmesg
Date: Tue, 21 Oct 2008 12:35:00 -0200 [thread overview]
Message-ID: <20081021143500.GA18469@ime.usp.br> (raw)
In-Reply-To: <20081021123348.GB15685@mit.edu>
First of all, Thanks Theodore.
On Oct 21 2008, Theodore Tso wrote:
> On Tue, Oct 21, 2008 at 08:15:10AM -0200, Rogério Brito wrote:
> > Did you sync the device? From the message, it seems that some data were
> > to be written to the device, but the device was already gone by that
> > time, but I'm not a specialist on the filesystem subsystem and perhaps
> > others could say more about it.
>
> A patch to suppress the WARN information will be in 2.6.28 when the
> user does something stupid (i.e., yank out a USB stick without
> unmounting the filesystem first).
Right. I will put a big, fat warning on the installation of usbmount and
tell the users about it. Besides that, depending on the filesystem, the
superblock may be marked as dirty.
> This was done mainly to suppress the "scary message" in dmesg, which on
> distributions that support uploading such messages to
> http://www.kerneloops.org for analysis, was cluttering the reports.
Right...
> > > > [39071.160167] Buffer I/O error on device sda1, logical block 1545
> > > > [39071.160170] lost page write due to I/O error on sda1
> > > > [39071.160184] Buffer I/O error on device sda1, logical block 1545
> > > > [39071.160187] lost page write due to I/O error on sda1
>
> These errors you'd still get, since these messages are the sound of
> users' data being irretrivably being lost.
Good that not all messages will be going... BTW, this reminded me of a
patch that eliminated a whole lot of messages (BUG()'s) for embedded
devices... I didn't find it anymore...
Also, the same thing with the hash tables that could turn into linked lists
eventually...
But I'm drifting away from the main topic.
> > Well, it is a bug. It just needs more investigation to see where the bug
> > lies.
>
> I don't know if you would call it a bug or not. Fundamentally,
> yanking out a USB stick without unmounting it first is dangerous, and
> can lead to data loss.
At least sync'ing...
[snip]
> If you see "lost page write due to I/O error", then you will have lost
> data due to premature removal of the USB stick, and fundamentally
> *that* bug exists between the keyboard and the chair.
Ok, so I'm closing this bug in the next upload.
Thanks, Rogério Brito.
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
next prev parent reply other threads:[~2008-10-21 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2bfaaf400810172145g4aba4827l87a19e67b9742815@mail.gmail.com>
2008-10-18 6:04 ` Bug#502583: scary messages in dmesg Rogério Brito
2008-10-20 23:54 ` Alexandre Lymberopoulos
2008-10-21 10:15 ` Rogério Brito
2008-10-21 12:33 ` Theodore Tso
2008-10-21 14:35 ` Rogério Brito [this message]
2008-10-21 15:31 ` Theodore Tso
2008-10-21 15:43 ` Jon Smirl
2008-10-21 21:21 ` Alexandre Lymberopoulos
2008-10-21 20:55 ` Alexandre Lymberopoulos
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=20081021143500.GA18469@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=502583-submitter@bugs.debian.org \
--cc=502583@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lymber@gmail.com \
--cc=rafael@debian.org \
--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 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.