Linux LVM users
 help / color / mirror / Atom feed
From: Adrian Head <ahead@bigpond.net.au>
To: Andreas Dilger <adilger@turbolabs.com>, Eric Sandeen <sandeen@sgi.com>
Cc: Linux XFS Mailing List <linux-xfs@oss.sgi.com>,
	linux-lvm@sistina.com, ext2-devel@lists.sourceforge.net
Subject: Re: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily
Date: Thu Jan 10 09:22:01 2002	[thread overview]
Message-ID: <E16Oh1M-0003UB-00@hermes.sistina.com> (raw)
In-Reply-To: <20020105142527.I12868@lynx.no>

In the process of trying to fix this issue I have been playing around with a 
patch from the great SGI XFS developers.  It certainly fixes the problems I 
was having but I'm now trying to help clean the patch up.

The problem now is that when I try to mount a ext3 snapshot using:
mount /dev/HDA/SNAP /mnt/snapshot
The kernel mounts the snapshot as ext2.  Is was not happening before the 
patch and I was wondering if anyone thinks this is a problem.  As ext3 is 
backward compatible with ext2 there doesn't seem to be any problems during my 
testing with respect to standard file operations.  I can mount the snapshot 
as ext3 if I use:
mount -t ext3 /dev/HDA/SNAP /mnt/snapshot

The next problem is that when the ext3 snapshot (mounted as ext3) overflows 
lvm generates an error in the logs:
lvm -- giving up to snapshot /dev/HDA/XFS on /dev/HDA/SNAP: out of space
lvm - lvm_map: ll_rw_blk for inactive LV /dev/HDA/SNAP

The 1st line I understand but the 2nd I don't.  I was hoping that some LVM 
guru/developer could explain the 2nd line and what it means.

The last problem is that in only some of my tests when I "ls" the overflowed 
snapshot "ls" complains about missing directories and files, "echo *" shows 
what use to be there and ext3 generates errors in the logs:
EXT3-fs error (device lvm(58,5)): ext3_readdir" directory #2 contains a hole 
at offset 0

I was hoping that a ext2/3 guru/developer could explain this error and what 
it means.

Thanks for everybodies time and effort.

-- 
Adrian Head

(Public Key available on request.)

  reply	other threads:[~2002-01-10  9:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200201020451.g024pPg00867@oss.sgi.com>
2002-01-04 13:49 ` [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily Eric Sandeen
2002-01-04 16:47   ` Adrian Head
2002-01-04 17:37     ` Andreas Dilger
2002-01-04 20:10       ` Adrian Head
2002-01-04 21:35       ` Adrian Head
2002-01-06  0:05         ` [linux-lvm] lvm-1.0.1rc4(ish) more robust on startup than lvm-1.0.1 Adrian Head
     [not found]       ` <200201050212.TAA16774@cthulhu.turbolabs.com>
2002-01-05 15:29         ` [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily Andreas Dilger
2002-01-10  9:22           ` Adrian Head [this message]
2002-01-10  9:28             ` Patrick Caulfield
2002-01-10 15:21               ` Adrian Head
2002-01-11  2:40             ` Luca Berra
     [not found]           ` <200201101521.IAA17651@cthulhu.turbolabs.com>
2002-01-10 14:14             ` Andreas Dilger
2002-01-10 15:02               ` Adrian Head
     [not found]   ` <200201042349.g04Nnag26320@oss.sgi.com>
2002-01-04 17:12     ` Eric Sandeen
2002-01-04 20:44       ` Adrian Head
2002-01-05 17:06         ` Andreas Dilger
     [not found]       ` <200201050346.g053kmg29738@oss.sgi.com>
2002-01-04 21:08         ` Eric Sandeen
2002-01-07  8:05           ` Adrian Head
2002-01-07 12:58           ` Eric Sandeen
2002-01-06  0:20         ` Adrian Head
2002-01-09 16:25 ` Eric Sandeen
2002-01-09 16:40   ` Eric Sandeen
     [not found] <200201071648.IAA08511@sgi.com>
2002-01-07 14:34 ` Keith Owens
     [not found] <200201071508.g07F8Pg14938@oss.sgi.com>
2002-01-07  8:39 ` Keith Owens
2002-01-07 10:48   ` Adrian Head
     [not found] <200201040015.RAA00441@cthulhu.turbolabs.com>
2002-01-03 18:36 ` Andreas Dilger
     [not found] <6u4rm4r53e.fsf@zork.zork.net>
     [not found] ` <200201031638.g03GcJg20734@oss.sgi.com>
     [not found]   ` <1010072497.12080.42.camel@jen.americas.sgi.com>
2002-01-03 18:13     ` Adrian Head

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=E16Oh1M-0003UB-00@hermes.sistina.com \
    --to=ahead@bigpond.net.au \
    --cc=adilger@turbolabs.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-lvm@sistina.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sandeen@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