public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Lawry <a_lawry@hotmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs, ubuntu, & xen
Date: Thu, 11 Sep 2008 22:00:39 -0500	[thread overview]
Message-ID: <48C9DB57.10909@sandeen.net> (raw)
In-Reply-To: <BLU141-W21A745812EB94C128504C680510@phx.gbl>

Andrew Lawry wrote:
> 
> Hi,
> 
> I am setting up a new Xen installation using XFS as the file system. On our test
> machine we have been having some problems with a domU crashing and some
> data loss on the domU (on recovery of the file system at the next boot
> some files have become truncated.

Why is the domU crashing; does it look at all related to these problems,
or is it something different?

Does the filesystem image check out ok with xfs_repair when this
happens?  If not, what does it find?

Which files are truncated, system files or files that were being written
at the time of the crash?  And just to be clear, what exactly do you
mean by truncated; that the data is correct up to EOF, but the file is
smaller than you expect?  Is this more than simply buffered writes
getting lost, which is to be expected?

-Eric

> Our setup:
> 
> Dom0 and
> domUs are Ubuntu 8.04 64 bit  Server edition. The domUs use tap file
> based backends. The file system holding the image files is XFS and the
> filesystem in each domU is also XFS.
> 
> We are using xen 3.2 packaged with ubuntu.
> 
> I
> have read on this mailing list and on google that xen and XFS do not
> work well together and some patches have been produced. Has this issue been addressed? Would those patches be in the stable release and have found their way into Ubuntu packages?
> 
> Thanks for your help.
> 
> Andrew

      reply	other threads:[~2008-09-12  2:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  2:04 Andrew Lawry
2008-09-12  3:00 ` Eric Sandeen [this message]

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=48C9DB57.10909@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=a_lawry@hotmail.com \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox