All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: 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: Thu, 04 Oct 2012 09:06:49 -0700	[thread overview]
Message-ID: <506DB419.2030902@tlinx.org> (raw)
In-Reply-To: <506DAF66.2030507@tlinx.org>



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
Ishtar:/# umount /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

---
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.

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)?


  

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-10-04 16:05 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 ` Linda Walsh [this message]
2012-10-04 23:37   ` how to replay log of a fs that has no log: is this supposed to work? SW Defect? Dave Chinner

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=506DB419.2030902@tlinx.org \
    --to=xfs@tlinx.org \
    --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 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.