From: Padraig Brady <padraig.brady@corvil.com>
To: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: ext3 fs: no userspace writes == no disk writes ?
Date: Fri, 20 Sep 2002 10:19:07 +0100 [thread overview]
Message-ID: <3D8AE80B.9090902@corvil.com> (raw)
In-Reply-To: 3D8AE719.5000901@corvil.com
Padraig Brady wrote:
> Rob van Nieuwkerk wrote:
>
>> Hi Pádraig,
>>
>> Pádraig Brady wrote:
>>
>>> Rob van Nieuwkerk wrote:
>>>
>>>> Hi Alan,
>>>>
>>>>
>>>>> On Fri, 2002-09-20 at 00:04, Andrew Morton wrote:
>>>>>
>>>>>
>>>>>> There are frequently written areas of an ext3 filesystem - the
>>>>>> journal, the superblock. Those would wear out pretty quickly.
>>>>>
>>>>>
>>>>> CF is -supposed- to wear level.
>>>>
>>>>
>>>> Yes I know.
>>>>
>>>> But I haven't been able to find any specs from any CF manufacturer
>>>> about this mechanism, percentage of spare sectors or number of allowed
>>>> write-cycles in general.
>>>
>>>
>>> me either.
>>>
>>> Why don't you just mount the fs ro ?
>>>
>>> Pádraig
>>
>>
>>
>> Ehm .., because I need to store data on it ..
>
>
> Ehm, well remount,rw before you store data on it
> and remount,ro when finished?
Note you can organise things (links from /etc/various /dev/various /var
to ramdisk/tmpfs/...) so that you never have to mount the CF rw.
Pádraig.
next prev parent reply other threads:[~2002-09-20 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 22:30 ext3 fs: no userspace writes == no disk writes ? Rob van Nieuwkerk
2002-09-19 23:04 ` Andrew Morton
2002-09-19 23:25 ` Alan Cox
2002-09-19 23:52 ` Rob van Nieuwkerk
2002-09-20 9:04 ` Padraig Brady
2002-09-20 9:09 ` Rob van Nieuwkerk
2002-09-20 9:15 ` Padraig Brady
2002-09-20 9:19 ` Padraig Brady [this message]
2002-09-20 9:26 ` Rob van Nieuwkerk
2002-09-20 9:23 ` Rob van Nieuwkerk
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 23:31 Ricardo Galli
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=3D8AE80B.9090902@corvil.com \
--to=padraig.brady@corvil.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robn@verdi.et.tudelft.nl \
/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