From: Chris Mason <mason@suse.com>
To: Neil Robinson <neilr@superbase.co.uk>
Cc: reiserfs-list@namesys.com
Subject: Re: 3.6.25 - Journal replayed back to 3 weeks ago
Date: Thu, 15 Jan 2004 12:56:08 -0500 [thread overview]
Message-ID: <1074189367.29546.40.camel@tiny.suse.com> (raw)
In-Reply-To: <1074184418.2397.84.camel@neilvaiogt.superbase.co.uk>
On Thu, 2004-01-15 at 11:33, Neil Robinson wrote:
> > Ok, please tell me more about the vmware setup. Is are the vmware
> > drives configured to do copy on write?
>
> According to the documentation, changes made to the virtual drives are
> committed to the physical drive immediately. Here is the salient info
> from the dmesg:
vmware has a mode where the changes are written to a log file instead of
to the main file. The client doesn't see things are split between two
files, since vmware exports them as a single device. This allows you to
do fancy things like roll back changes, or share a base file between two
hosts and have changes to into private files.
It's possible that you're in this mode and somehow lost a log file.
Are the virtual drives being exported to linux real block devices in
windows, or are the files on some windows filesystem?
-chris
next prev parent reply other threads:[~2004-01-15 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 18:47 3.6.25 - Journal replayed back to 3 weeks ago Neil Robinson
2004-01-12 19:04 ` Chris Mason
2004-01-12 19:44 ` Neil Robinson
2004-01-15 5:23 ` Neil Robinson
2004-01-15 14:53 ` Chris Mason
2004-01-15 16:33 ` Neil Robinson
2004-01-15 17:56 ` Chris Mason [this message]
2004-01-15 19:19 ` Neil Robinson
2004-01-15 19:35 ` Chris Mason
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=1074189367.29546.40.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=neilr@superbase.co.uk \
--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.