From: Dave Chinner <david@fromorbit.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: how to replay log of a fs that has no log: is this supposed to work? SW Defect?
Date: Fri, 5 Oct 2012 09:37:54 +1000 [thread overview]
Message-ID: <20121004233754.GC23644@dastard> (raw)
In-Reply-To: <506DB419.2030902@tlinx.org>
On Thu, Oct 04, 2012 at 09:06:49AM -0700, Linda Walsh wrote:
>
>
> Linda Walsh wrote:
> (blah blah blah)...
>
> or more specifically:
>
> xfs_freeze -f /home/.snapdir/\@GMT-2012.10.04-03.06.17
> Ishtar:/# xfs_ncheck /dev/Home+Space/Home-2012.10.04-03.06.17
>
> ERROR: The filesystem has valuable metadata changes in a log which needs to
> be replayed. Mount the filesystem to replay the log, and unmount it before
> re-running xfs_ncheck. If you are unable to mount the filesystem, then use
> the xfs_repair -L option to destroy the log and attempt a repair.
> Note that destroying the log may cause corruption -- please attempt a mount
> of the filesystem before doing this.
> must run blockget -n first
>
> ok -- lets mount/umount it:
> Ishtar:/# mount -o ro,nouuid
> /dev/Home+Space/Home-2012.10.04-03.06.17
> /home/.snapdir/@GMT-2012.10.04-03.06.17
So, a read only snapshot? If so what makes you think that recovery
can run and modify the filesystem/log?
THe whole point of freeze creating a consistent disk image is so you
can mount it without needing recovery to run. i.e:
# mount -o ro,nouuid,norecovery ....
> ---
> Um... looking at the above it would appear that I froze a fs.
> ncheck claimed the freeze didn't result in the logfile being written being put
> into a consistent state, but said to remount the fs to allow it to play then
> umount...
>
> So... did that.
> Log file is still in a corrupt state.
The log is not corrupt, just dirty.
> Am I wrong in assuming that doing xfs_repair -L to destroy the log on this
> dev, might be a bad thing to do and might screw up it's "Origin" file
> system (i.e. the current 'live' /home partition)?
It will try to write to the snapshot. If it is a read-only
snapshot...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-10-04 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 15:46 how to replay log of a fs that has no log? or is this supposed to work? Linda Walsh
2012-10-04 16:06 ` how to replay log of a fs that has no log: is this supposed to work? SW Defect? Linda Walsh
2012-10-04 23:37 ` Dave Chinner [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=20121004233754.GC23644@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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