All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: Samuel Thibault <samuel.thibault@inria.fr>,
	xen-devel@lists.xensource.com
Subject: Re: pvgrub and single partition VM
Date: Tue, 03 Feb 2009 16:04:15 +0100	[thread overview]
Message-ID: <49885CEF.9030704@inria.fr> (raw)
In-Reply-To: <20090120232743.GA5202@const.famille.thibault.fr>

Samuel Thibault a écrit :
> Samuel Thibault, le Tue 20 Jan 2009 16:17:44 +0100, a écrit :
>> Guillaume Rousse, le Tue 20 Jan 2009 15:48:55 +0100, a écrit :
>>> And I can mount the partition from dom0 without problem. I have to check 
>>> if ext3 support is not missing from pvgrub,
>> There is no need for any particular support for ext3, as while unmounted
>> that's just ext2.  And the 256byte inode patch is applied while
>> building.  I thus wonder what the problem can be.
> 
> I've just checked again, I could run configfile (hd0)/boot/blabla on a
> freshly formatted ext3 volume.  In case you are using some non-default
> option that annoys grub, could you send us the output of
> tune2fs -l yourpartition
> ?
Sorry for the delay, I've been occupied by other task.

Here it is:
[root@sequoia ~]# tune2fs -l /dev/iscsi/sn.101200926/lun9/part1
tune2fs 1.41.2 (02-Oct-2008)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          9c8962e1-d521-4bbf-8dad-c92b0077d61e
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index 
filetype sparse_super large_file
Filesystem flags:         signed_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1310720
Block count:              5242876
Reserved block count:     262143
Free blocks:              5059920
Free inodes:              1279106
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1022
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Tue Feb  3 15:42:35 2009
Last mount time:          Tue Feb  3 15:50:22 2009
Last write time:          Tue Feb  3 15:58:30 2009
Mount count:              2
Maximum mount count:      29
Last checked:             Tue Feb  3 15:42:35 2009
Check interval:           15552000 (6 months)
Next check after:         Sun Aug  2 16:42:35 2009
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      65b6279d-5265-40b1-9e16-afbf6335005f
Journal backup:           inode blocks

This is an ISCSI device.

      parent reply	other threads:[~2009-02-03 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 10:57 pvgrub and single partition VM Guillaume Rousse
     [not found] ` <20090120110509.GH5147@const.bordeaux.inria.fr>
2009-01-20 14:48   ` Guillaume Rousse
     [not found]     ` <20090120151744.GB5177@const.bordeaux.inria.fr>
     [not found]       ` <20090120232743.GA5202@const.famille.thibault.fr>
2009-02-03 15:04         ` Guillaume Rousse [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=49885CEF.9030704@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=samuel.thibault@inria.fr \
    --cc=xen-devel@lists.xensource.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.