[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2e108260805261028o204d4fc7l3f20ad3919cf778b@mail.gmail.com>
Date: Mon, 26 May 2008 19:28:23 +0200
From: "Bart Van Assche" <bart.vanassche@...il.com>
To: "Oliver Neukum" <oliver@...kum.org>
Cc: "Theodore Tso" <tytso@....edu>, "Ingo Molnar" <mingo@...e.hu>,
"Jan Kara" <jack@...e.cz>,
"Arjan van de Ven" <arjan@...ux.intel.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Greg KH" <greg@...ah.com>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: Top 10 bugs/warnings for the week of March 23rd, 2008
On Mon, May 26, 2008 at 7:09 PM, Oliver Neukum <oliver@...kum.org> wrote:
> Am Montag 26 Mai 2008 19:01:48 schrieb Theodore Tso:
>> If the USB stack folks would like to work on how to recognize that
>> it's the same USB stick that had been previously pulled, so that it
>> gets the same block device, and we can decide for how long we should
>> keep dirty buffers around associated with a pulled USB stick, we can
>> certainly have that conversation. :-)
>
> Even if we could tell whether the device has remained the same, how
> would we know the medium wasn't exchanged?
Looking at the filesystem UUID could help -- this is an ID that is
present as data on the disk, and that is even independent of the bus
type. See also /dev/disk/by-uuid.
For the journaling filesystems I am familiar with the default value
for the commit parameter is 5 seconds. Would it be a good idea to
leave the default to 5s for non-removable devices, and to change this
default to 1s for removable devices ?
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists