From: Christoph Hellwig <hch@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, hgichon <kpkim@gluesys.com>
Subject: Re: Announce: unlimited number of shared snapshots
Date: Tue, 2 Dec 2008 02:34:43 -0500 [thread overview]
Message-ID: <20081202073443.GA22985@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0812020140540.28552@hs20-bc2-1.build.redhat.com>
On Tue, Dec 02, 2008 at 02:05:28AM -0500, Mikulas Patocka wrote:
> Hi
>
> I fixed the ext2 bug (it was unsupported handling of buffer readahead) ---
> download the new version of patches from the same location.
>
> I couldn't reproduce the XFS bug. Please retry. Are you sure that you
> didn't try to mount the _snapshot_ as XFS? Snapshots are currently not
> writeable (they will be writeable in the final version), so attempting to
> mount the snapshot read/write would return i/o error to the filesystem and
> produce an error message similar to the one displayed.
The error message definitively looks like trying to mount a r/o snapshots
without -o ro,norecovery:
> > fs/xfs/xfs_rw.c. Return address = 0xffffffff8037d399
> > [ 2696.363710] Filesystem "dm-3": I/O Error Detected. Shutting down
> > filesystem: dm-3
> > [ 2696.368085] Please umount the filesystem, and rectify the problem(s)
> > [ 2696.371756] I/O error in filesystem ("dm-3") meta-data dev dm-3 block
> > 0x200022 ("xlog_bwrite") error 5 buf count 2097152
> > [ 2696.378402] XFS: failed to locate log tail
> > [ 2696.380797] XFS: log mount/recovery failed: error 5
> > [ 2696.405586] XFS: log mount failed
next prev parent reply other threads:[~2008-12-02 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <492FAF1C.8080401@gluesys.com>
2008-11-28 19:54 ` Re:Announce: unlimited number of shared snapshots Mikulas Patocka
[not found] ` <4933684F.9060606@gluesys.com>
2008-12-02 7:05 ` Announce: " Mikulas Patocka
2008-12-02 7:34 ` Christoph Hellwig [this message]
[not found] ` <4936187D.1000302@gluesys.com>
2008-12-04 3:27 ` Mikulas Patocka
2008-11-27 5:41 Mikulas Patocka
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=20081202073443.GA22985@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=kpkim@gluesys.com \
--cc=mpatocka@redhat.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.