From: Enrico Weigelt <weigelt@metux.de>
To: linux kernel list <linux-kernel@vger.kernel.org>
Subject: reparing / editing filesystem while mounted
Date: Fri, 16 Sep 2005 19:45:59 +0200 [thread overview]
Message-ID: <20050916174559.GA247@nibiru.local> (raw)
Hi folks,
I've sometimes the situation where I'd like to edit or fsck a
currently mounted filesystem. Of course this really dangerous.
It would be great if there was an API for low-level filesystem
access, ie. directly changing data blocks, directory entries,
inodes, etc. The (modified) fs driver sitting behind it can so
take care that we dont have collision with the other fs operations,
ie. proper locking, buffer flushing, etc.
The modified fsck now entirely works with this API.
This API for example could provide:
+ superblock access
+ directory changes w/o inode access
-> sometimes we've got broken dirents which cannot be
changed/removed by normal fs operation (unlink(),etc)
often the user's already happy with clearing them.
-> if we've got a lost inode, we can connect it to some
dir (ie /lost+found) manually this way
+ inode changes
-> undeleting inodes
-> fixing wrong refcnts
-> clearing broken inodes / block tables, etc.
...
We probably need some journaling/messaging system so the kernel
can tell the userland fsck when something important changes, ie.
if we're checking directory connectivity and some dirent changes.
Of course this would all be very fs specific. But its implemented
at least for the most important disk fs'es (ie ext2/3) it would
be a great help for people running 24/7 online systems.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service
phone: +49 36207 519931 www: http://www.metux.de/
fax: +49 36207 519932 email: contact@metux.de
cellphone: +49 174 7066481
---------------------------------------------------------------------
-- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops --
---------------------------------------------------------------------
reply other threads:[~2005-09-16 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050916174559.GA247@nibiru.local \
--to=weigelt@metux.de \
--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®