[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Bad experience in mounting a domU disk


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Alain Barthe" <ab266061@xxxxxxxxx>
  • Date: Wed, 4 Jun 2008 17:47:07 +0200
  • Delivery-date: Wed, 04 Jun 2008 08:47:51 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=x1vlHHAbHUfqDRkkJE3lun9eWraGmCAZViJHVGpCggnxC3rSZl/0fgCbItIvy8TB8B 0O+jg467xGFCLDxz1UsPrsIiZibpwTybBIFOZl9UnRPsjddc5ZcC2/VBtJ7L+J1gZ0Pt mNKPD4cI8r+cmgnLPsyr083xW2bFK+iIBboXg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

2008/6/4 Rafał Kupka <rkupka+Listy.Xen@xxxxxxxxxxxxx>:
On Wed, Jun 04, 2008 at 11:00:43AM +0200, Alain Barthe wrote:

Many journalled filesystems do replay journal even if mounted with 'ro'
option. XFS has norecovery option to truly read-only disk access.
Similar option has been recently added to ext3.

I think that the best approach is to take LVM snapshot of domU
filesystem and then mount (with journal replayed) that snapshot.

Thanks Rafal and Javier for your explanation, I begin to understand what happened.

The ext3 fs has the option "noload" to disable the load of the journal. I looked for something like "nocache" to disable the cache, but it appears not to exist.

My goal in mounting the filesystem of a alive domU is to monitor it (content of key files, free space, etc) in a non intrusive manner. Dealing with LVM snapshot is not obvious as we have no place enough for that.

Does somebody have a similar need ?

Thanks again.

Alain.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.