Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
/: Not a XFS mount point. Why?
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Mon Jul 01, 2019 10:31 am    Post subject: /: Not a XFS mount point. Why? Reply with quote

I have root on M.2 SSD with XFS. Everything works except
Code:
~ $ sudo xfs_info /dev/sdd1
/: cannot find mount point.

Code:
 ~ $ sudo xfs_scrub /
EXPERIMENTAL xfs_scrub program in use! Use at your own risk!
/: Not a XFS mount point.

but
Code:
~ $ mount | grep -i sdd1
/dev/sdd1 on / type xfs (rw,noatime,attr2,inode64,noquota)

Code:
 ~ $ grep -i root /etc/mtab
/dev/root / xfs rw,noatime,attr2,inode64,noquota 0 0

Code:
 ~ $ cat /etc/fstab
PARTUUID=d6740b16-a968-42f4-a774-2412c35a96aa           /                       xfs     rw,noatime,attr2,inode64,allocsize=1048576k,logbsize=256k,noquota                                       0 0


My config - http://dpaste.com/017VSMC


Last edited by Perfect Gentleman on Thu Jul 04, 2019 1:38 pm; edited 2 times in total
Back to top
View user's profile Send private message
mike155
Veteran
Veteran


Joined: 17 Sep 2010
Posts: 1990
Location: Frankfurt, Germany

PostPosted: Mon Jul 01, 2019 11:18 am    Post subject: Reply with quote

What happens if you run the failing commands without sudo (directly as root)?
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Mon Jul 01, 2019 12:34 pm    Post subject: Reply with quote

the same.
Code:
 ~ $ sudo xfs_info /dev/sda1
meta-data=/dev/sda1              isize=512    agcount=32, agsize=7325939 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=0
data     =                       bsize=1024   blocks=234430023, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=1024   blocks=131072, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

 ~ $ sudo xfs_info /dev/sdd1
/: cannot find mount point.

sda is SATA-SSD.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Thu Jul 04, 2019 1:38 pm    Post subject: Reply with quote

anyone? help.
Back to top
View user's profile Send private message
mike155
Veteran
Veteran


Joined: 17 Sep 2010
Posts: 1990
Location: Frankfurt, Germany

PostPosted: Thu Jul 04, 2019 11:50 pm    Post subject: Reply with quote

What happens if you specify the mount-point instead of the block-device?
Code:
xfs_info /

man xfs_info wrote:
Code:
xfs_info [ -t mtab ] [ mount-point | block-device | file-image ]
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Fri Jul 05, 2019 1:18 am    Post subject: Reply with quote

Code:
~ $ sudo xfs_info /
/: cannot find mount point.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7506
Location: Saint Amant, Acadiana

PostPosted: Fri Jul 05, 2019 1:30 am    Post subject: Reply with quote

Probably an XFS bug, despite being a mature filesystem it may have difficulties with SSD. I had some issue in past with XFS being directly on HDD, without partitioning. Don't remember what it was, something minor, but still a failure.
In any case, there are better filesystems for flash storage, I use F2FS for root filesystem myself.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Fri Jul 05, 2019 2:25 am    Post subject: Reply with quote

I used F2FS before that, but it became corrupted after power outage.
The problem is that it is okay with non-root SATA-SSD, and it is okay from live-usb Fredora. But it is not okay from my system.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7506
Location: Saint Amant, Acadiana

PostPosted: Fri Jul 05, 2019 2:29 am    Post subject: Reply with quote

XFS gets corrupted, too. Higher the performance of filesystem more likely the corruption in case of power loss. It depends on how much data is buffered and not written to the drive when power goes off. This is why UPS was invented.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Fri Jul 05, 2019 2:33 am    Post subject: Reply with quote

I've never had problems with XFS v5. Next kernel upgrade I'll try to define 'rootfstype' and 'rootflags' in bootparams and check it out again.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7506
Location: Saint Amant, Acadiana

PostPosted: Fri Jul 05, 2019 2:38 am    Post subject: Reply with quote

Perfect Gentleman wrote:
I've never had problems with XFS v5. Next kernel upgrade I'll try to define 'rootfstype' and 'rootflags' in bootparams and check it out again.

This is nonsense argument. Some drive drunk every day and won't get caught. Probably have version 5 alcohol in their blood?
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Fri Jul 05, 2019 2:42 am    Post subject: Reply with quote

okay.
I used F2FS twice. Every time it died eventually after power outage. I use XFS third time and it is always okay.
Anyway it's not what this topic was created for.
I want to know what it is wrong with my system or maybe it is a bug in XFS or xfsprogs.
Back to top
View user's profile Send private message
axl
l33t
l33t


Joined: 11 Oct 2002
Posts: 925
Location: Romania

PostPosted: Fri Jul 05, 2019 9:55 am    Post subject: Reply with quote

You said that particular partition is your rootfs. Is it also the boot partition that contains grub?

If the answer is yes, then most likely that partition was made with -mcrc=0, which turns off the scrubbing. And as far as I know and remember, if crc=1, then it can't be used for grub, because grub doesn't understand partitions with crc=1 (yet).

Still, it is weird that xfs_info doesn't work on it. That should have worked regardless of crc=1 or 0.
Back to top
View user's profile Send private message
mike155
Veteran
Veteran


Joined: 17 Sep 2010
Posts: 1990
Location: Frankfurt, Germany

PostPosted: Fri Jul 05, 2019 10:10 am    Post subject: Reply with quote

Quote:
I want to know what it is wrong with my system or maybe it is a bug in XFS or xfsprogs.

Run
Code:
cat /usr/sbin/xfs_info

It's a short shell script! It calls other programs like "findmnt" from util-linux. It's likely that your machine and xfs_info are fine, but that the output of one of the called programs has changed.

Run the xfs_info in debug mode and/or run the called programs manually (with the arguments used in the script). Compare the output for /dev/sda1 and /dev/sdd1. It should be possible to find the culprit :-)
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Jul 06, 2019 1:35 pm    Post subject: Reply with quote

Quote:
Is it also the boot partition that contains grub?

No, I use EFISTUB.
Code:
sdd                                                                           
└─sdd1 xfs    PX-G256M6e   681c1a22-4084-41c7-9c09-42a978436e34  202.8G    15% /
sde                                                                           
└─sde1 vfat                EC01-5458                               7.4G     0% /boot


Code:
 ~ $ cat /usr/sbin/xfs_info
#!/bin/sh -f
# SPDX-License-Identifier: GPL-2.0
#
# Copyright (c) 2000-2001 Silicon Graphics, Inc.  All Rights Reserved.
#

OPTS=""
USAGE="Usage: xfs_info [-V] [-t mtab] [mountpoint|device|file]"

# Try to find a loop device associated with a file.  We only want to return
# one loopdev (multiple loop devices can attach to a single file) so we grab
# the last line and return it if it's actually a block device.
try_find_loop_dev_for_file() {
        local x="$(losetup -O NAME -j "$1" 2> /dev/null | tail -n 1)"
        test -b "$x" && echo "$x"
}

while getopts "t:V" c
do
        case $c in
        t)      OPTS="-t $OPTARG" ;;
        V)      xfs_spaceman -p xfs_info -V
                status=$?
                exit $status
                ;;
        *)      echo $USAGE 1>&2
                exit 2
                ;;
        esac
done
set -- extra "$@"
shift $OPTIND
case $# in
        1)
                arg="$1"

                # See if we can map the arg to a loop device
                loopdev="$(try_find_loop_dev_for_file "${arg}")"
                test -n "${loopdev}" && arg="${loopdev}"

                # If we find a mountpoint for the device, do a live query;
                # otherwise try reading the fs with xfs_db.
                if mountpt="$(findmnt -f -n -o TARGET "${arg}" 2> /dev/null)"; then
                        xfs_spaceman -p xfs_info -c "info" $OPTS "${mountpt}"
                        status=$?
                else
                        xfs_db -p xfs_info -c "info" $OPTS "${arg}"
                        status=$?
                fi
                ;;
        *)      echo $USAGE 1>&2
                exit 2
                ;;
esac
exit $status

Code:
~ $ findmnt
TARGET                       SOURCE      FSTYPE     OPTIONS
/                            /dev/sdd1   xfs        rw,noatime,attr2,inode64,noquota
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Jul 06, 2019 1:51 pm    Post subject: Reply with quote

Code:
~ $ findmnt -f -n -o TARGET /dev/sdd1
/

Code:
~ $ findmnt -f -n -o TARGET /dev/sda1
/home/MZ7WD240HAFV

It seems 'findmnt' works fine.
Back to top
View user's profile Send private message
mike155
Veteran
Veteran


Joined: 17 Sep 2010
Posts: 1990
Location: Frankfurt, Germany

PostPosted: Sat Jul 06, 2019 3:12 pm    Post subject: Reply with quote

Quote:
It seems 'findmnt' works fine.

I agree! :-)

Please post the output of
Code:
bash -x /usr/sbin/xfs_info /dev/sda1
and of
Code:
bash -x /usr/sbin/xfs_info /dev/sdd1

It will tell us how the "real" program (xfs_db or xfs_spaceman) is called
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Jul 06, 2019 3:20 pm    Post subject: Reply with quote

Code:
 ~ $ bash -x /usr/sbin/xfs_info /dev/sda1
+ OPTS=
+ USAGE='Usage: xfs_info [-V] [-t mtab] [mountpoint|device|file]'
+ getopts t:V c
+ set -- extra /dev/sda1
+ shift 1
+ case $# in
+ arg=/dev/sda1
++ try_find_loop_dev_for_file /dev/sda1
+++ losetup -O NAME -j /dev/sda1
+++ tail -n 1
++ local x=
++ test -b ''
+ loopdev=
+ test -n ''
++ findmnt -f -n -o TARGET /dev/sda1
+ mountpt=/home/MZ7WD240HAFV
+ xfs_spaceman -p xfs_info -c info /home/MZ7WD240HAFV
meta-data=/dev/sda1              isize=512    agcount=32, agsize=7325939 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=0
data     =                       bsize=1024   blocks=234430023, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=1024   blocks=131072, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
+ status=0
+ exit 0


Code:
 ~ $ bash -x /usr/sbin/xfs_info /dev/sdd1
+ OPTS=
+ USAGE='Usage: xfs_info [-V] [-t mtab] [mountpoint|device|file]'
+ getopts t:V c
+ set -- extra /dev/sdd1
+ shift 1
+ case $# in
+ arg=/dev/sdd1
++ try_find_loop_dev_for_file /dev/sdd1
+++ losetup -O NAME -j /dev/sdd1
+++ tail -n 1
++ local x=
++ test -b ''
+ loopdev=
+ test -n ''
++ findmnt -f -n -o TARGET /dev/sdd1
+ mountpt=/
+ xfs_spaceman -p xfs_info -c info /
/: cannot find mount point.+ status=1
+ exit 1
Back to top
View user's profile Send private message
axl
l33t
l33t


Joined: 11 Oct 2002
Posts: 925
Location: Romania

PostPosted: Sat Jul 06, 2019 3:24 pm    Post subject: Reply with quote

I noticed you have partuuid in fstab. I hope you have device-mapper and whatever required for every system part to read that, but let's just assume that is wrong and test how would things work if you had /dev/sdd1 in fstab instead of partuuid. I have no other idea, based on what I seed. Maybe the output from blkid to check the partuuid.
Back to top
View user's profile Send private message
axl
l33t
l33t


Joined: 11 Oct 2002
Posts: 925
Location: Romania

PostPosted: Sat Jul 06, 2019 3:28 pm    Post subject: Reply with quote

and I think i'm right. according to your post to me about efistubs, your partuuid should be 681c1a22-4084-41c7-9c09-42a978436e34, but according to another post (the fstab one), it should be d6740b16-a968-42f4-a774-2412c35a96aa.

let me refrase that. according to your post to me, the correct partuuid is 681c1a22-4084-41c7-9c09-42a978436e34, but instead in fstab it is (wrong) d6740b16-a968-42f4-a774-2412c35a96aa.

Am 99% sure this is correct. let us know how it goes.
Back to top
View user's profile Send private message
axl
l33t
l33t


Joined: 11 Oct 2002
Posts: 925
Location: Romania

PostPosted: Sat Jul 06, 2019 3:32 pm    Post subject: Reply with quote

I'm guessing, you tar-ed the old gentoo when you bought the ssd, and didn't change in fstab the new partuuid after you un-tar-ed the old distro onto the new drive.

You mentioned an M2. I'm guessing that's new. And every other little piece falls into place. :)
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Jul 06, 2019 3:37 pm    Post subject: Reply with quote

PARTUUID is right.
Code:
/dev/sdd1: LABEL="PX-G256M6e" UUID="681c1a22-4084-41c7-9c09-42a978436e34" TYPE="xfs" PARTLABEL="PX-G256M6e" PARTUUID="d6740b16-a968-42f4-a774-2412c35a96aa"
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Jul 06, 2019 3:40 pm    Post subject: Reply with quote

axl wrote:
I'm guessing, you tar-ed the old gentoo when you bought the ssd, and didn't change in fstab the new partuuid after you un-tar-ed the old distro onto the new drive.

No, it's new install, rather fresh, end of April.
Back to top
View user's profile Send private message
axl
l33t
l33t


Joined: 11 Oct 2002
Posts: 925
Location: Romania

PostPosted: Sat Jul 06, 2019 3:43 pm    Post subject: Reply with quote

Perfect Gentleman wrote:
PARTUUID is right.
Code:
/dev/sdd1: LABEL="PX-G256M6e" UUID="681c1a22-4084-41c7-9c09-42a978436e34" TYPE="xfs" PARTLABEL="PX-G256M6e" PARTUUID="d6740b16-a968-42f4-a774-2412c35a96aa"


No it's not. PARTUUID != UUID. if fstab says PARTUUID... then use that, not the UUID. Its' right there.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 921

PostPosted: Sat Jul 06, 2019 3:46 pm    Post subject: Reply with quote

I don't get it. I know that PARTUUID != UUID. And I use PARTUUID for root device.
Code:
PARTUUID=d6740b16-a968-42f4-a774-2412c35a96aa           /                       xfs     rw,noatime,attr2,inode64,allocsize=1048576k,logbsize=256k,noquota                                       0 0

Or you want me to use UUID instead of PARTUUID, don't you?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum