From: Digital Parasite <digital.parasite@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: NTFS forced dirty mount in read/write mode?
Date: Thu, 21 Apr 2005 10:55:59 -0400 [thread overview]
Message-ID: <78b577ee05042107552f5a9603@mail.gmail.com> (raw)
In-Reply-To: <78b577ee05041912127e8d0199@mail.gmail.com>
Hello,
I am using a Linux 2.6.11 based system and love the ability for the
new NTFS driver to mount the file-system as read/write.
The problem that I am having is if I mount an NTFS partition, then the
machine loses power or the machine is rebooted without explicitly
unmounting the partition, I can then only mount it as read-only and
get the message:
"NTFS-fs error (device hda1): load_system_files(): Volume is dirty..."
That is even if all I do is mount the filesystem but do not perform
any reads/writes, and the system gets rebooted.
Is there any way to force Linux to mount the partition read/write even
though it is dirty? I am not be able to boot into Windows to run
chkdsk from there to correct the problem so what are my options?
Since there is no way to add or remove files on an NTFS filesystem
with the curren driver, only update the contents of existing files, is
it even a problem for the volume to be dirty? Nothing in the volume
bitmap would be changing right?
If it was possible to force a read/write mount when the volume is
dirty, when you then unmounted the system, would it bring the log
files back into sync so it would no longer be dirty? By dirty, I'm
guessing there is some discrepency between the primary and backup NTFS
bitmap/log files right?
Thanks in advance,
DP
next parent reply other threads:[~2005-04-21 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <78b577ee05041912127e8d0199@mail.gmail.com>
2005-04-21 14:55 ` Digital Parasite [this message]
2005-04-21 15:27 ` NTFS forced dirty mount in read/write mode? Anton Altaparmakov
2005-04-22 12:37 ` Yura Pakhuchiy
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=78b577ee05042107552f5a9603@mail.gmail.com \
--to=digital.parasite@gmail.com \
--cc=linux-fsdevel@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 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.