All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Joseph <joseph.yang@xtaotech.com>
To: Dave Chinner <david@fromorbit.com>, Eric Sandeen <sandeen@sandeen.net>
Cc: sandeen@redhat.com, nathans@debian.org, linux-xfs@vger.kernel.org
Subject: Re: xfs_repair: add '-F' option to ignore writable mount checking
Date: Tue, 27 Feb 2018 18:44:35 +0800	[thread overview]
Message-ID: <5A953693.8080101@xtaotech.com> (raw)
In-Reply-To: <20180224220428.GB30854@dastard>

xfs_repair should not touch non-xfs mountpoints in platform_check_mount().
If non-xfs mountpoints can be filtered out, the dead fuse mountpoint can
never block our xfs_repair. The following patch can fix my problem and not
add dangerous option to xfs_repair.

thx,

Yang Honggang

-------------------------new patch----------------------
diff --git a/libxfs/linux.c b/libxfs/linux.c
index 0bace3e..6ad24ce 100644
--- a/libxfs/linux.c
+++ b/libxfs/linux.c
@@ -44,6 +44,7 @@ static int max_block_alignment;
  #endif

  #define PROC_MOUNTED   "/proc/mounts"
+#define MNTTYPE_XFS        "xfs"

  /*
   * Check if the filesystem is mounted.  Be verbose if asked, and
@@ -78,6 +79,9 @@ platform_check_mount(char *name, char *block, struct 
stat *s, int flags)
                 return 1;
         }
         while ((mnt = getmntent(f)) != NULL) {
+               /* filter out non xfs mountpoint */
+               if (strncmp(mnt->mnt_type, MNTTYPE_XFS, 
strlen(mnt->mnt_type)))
+                       continue;
                 if (stat(mnt->mnt_dir, &mst) < 0)
                         continue;
                 if (mst.st_dev != s->st_rdev)
-------------------------new patch end-----------------

On 02/25/2018 06:04 AM, Dave Chinner wrote:
> On Sat, Feb 24, 2018 at 11:56:44AM -0600, Eric Sandeen wrote:
>> On 2/24/18 5:23 AM, Yang Joseph wrote:
>>> hello,
>>>
>>> Before the repair process, xfs_repair will check if user specified device already
>>> has a writable mountpoint. And it will stat all the mountpoints of the system. If there
>>> is a dead mountpoint, this checking will be blocked and xfs_repair will enter 'D' state.
> So why is the mount point dead?
>
> That kinda means that the filesystem is still mounted, but something
> has hung somewhere and the filesystem may still have active
> references to the underlying device and be doing stuff that is
> modifying the filesystem....
>
> And if the device is still busy, then you aren't going to be able to
> mount the repaired device, anyway, because the block device is still
> busy...
>
>> That sounds like a bug worth fixing, but I am much
>> less excited about adding options which could do serious damage
>> to a filesystem.
> TO me it sounds like something that should be fixed by a reboot, not
> by adding dangerous options to xfs_repair...
>
> Cheers,
>
> Dave.


  parent reply	other threads:[~2018-02-27 10:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24 11:23 xfs_repair: add '-F' option to ignore writable mount checking Yang Joseph
2018-02-24 17:56 ` Eric Sandeen
2018-02-24 22:04   ` Dave Chinner
2018-02-24 22:08     ` Eric Sandeen
2018-02-26  2:59     ` Yang Joseph
2018-02-26 12:02       ` Carlos Maiolino
2018-02-26 12:19       ` Brian Foster
2018-02-27 10:44     ` Yang Joseph [this message]
2018-02-27 10:57       ` Carlos Maiolino
2018-02-27 14:47       ` Eric Sandeen
2018-02-28  3:31         ` Yang Joseph
2018-02-28  3:34         ` Yang Joseph
     [not found] <5A97638A.9050509@xtaotech.com>
2018-03-01  2:31 ` Yang Joseph
2018-03-02  6:23   ` Yang Joseph

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=5A953693.8080101@xtaotech.com \
    --to=joseph.yang@xtaotech.com \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nathans@debian.org \
    --cc=sandeen@redhat.com \
    --cc=sandeen@sandeen.net \
    /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.