From: Spam <spam@tnonline.net>
To: reiserfs-list@namesys.com
Subject: Re: nvram to protect fs during power loss?
Date: Fri, 31 Dec 2004 13:45:32 +0100 [thread overview]
Message-ID: <273759260.20041231134532@tnonline.net> (raw)
In-Reply-To: <20041231094126.GV1586@hvs.envisage.co.za>
Yes, I know that good hardware already do use battery backups and
similar. But I was talking about normal consumer hardware; desktops,
laptops, etc.
I do not know how the internals of reiser4 works, but one of the
problems said to be that it cannot be certain about the order and
integrity of the data if a power failure occur. But if reiser4
stored some kind of index number, key etc, on regular intervals then
that could certainly help in recovering the filesystem to a working
state.
As it is now you can end up with a severely broken filesystem that
doesn't even mount if you have a power failure. IMO a filesystem
should do its best to protect the data on it. I thought that perhaps
using NVRAM could aid in the recovery after the powerloss, instead
of tossing a user "bad error, use --build-sb to fix" during next
boot.
~S
> On Fri, Dec 31, 2004 at 12:40:08AM +0100, Spam wrote:
>>
>> There have been some discussions about recovery abilities during
>> power loss if write cache is enabled. Some recovery tool I saw once
>> used NVRAM to store progress info so that if you had a power loss it
>> would be able to resume.
> Typically specialized hardware, typically used for NFS (which is stateless) doing
> "caching" of the writes to enhance performance.
>> Perhaps it would be possible for Reiser4 to store some info, like
>> time indexes etc in NVRAMwhen it send sync commands to the disk.
>> This way it might be possible to avoid corruptions by simply
>> verifying (fsck) the data stored after that time index etc?
> The way the journals/logs does??
´
--
next prev parent reply other threads:[~2004-12-31 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 23:40 nvram to protect fs during power loss? Spam
2004-12-31 9:41 ` Hendrik Visage
2004-12-31 12:45 ` Spam [this message]
2004-12-31 16:46 ` Hendrik Visage
2004-12-31 16:51 ` Nick Vahalik
2004-12-31 17:28 ` Spam
2004-12-31 17:33 ` Hendrik Visage
2004-12-31 18:13 ` Chris Dukes
2004-12-31 19:02 ` Hendrik Visage
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=273759260.20041231134532@tnonline.net \
--to=spam@tnonline.net \
--cc=reiserfs-list@namesys.com \
/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.