You are not logged in.
last Monday (11/14/2011) my system was able to mount an external drive with an xfs filesystem on it.
as of today (11/21/2011) it no longer recognizes xfs:
% mount <my_dir>
mount: unknown filesystem type 'xfs'
does anyone else have this problem? i searched and didn't see anything in the forums.
Last edited by djg1971 (2011-11-21 22:24:52)
Offline
Odd... I'm assuming that xfsprogs are installed? Is there anything of note in your dmesg or errors.log?
Last edited by graysky (2011-11-21 21:03:15)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
graysky: thanks for responding.
yes, xfsprogs is installed (xfsprogs 3.1.7-1 to be exact).
dmesg only says that it sees the disk just fine:
_________________________
[14795.651276] usb 2-2: USB disconnect, device number 2
[14795.653229] sd 5:0:0:0: [sdb] Synchronizing SCSI cache
[14795.653264] sd 5:0:0:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00
[19343.468136] usb 2-2: new high speed USB device number 5 using ehci_hcd
[19343.609541] scsi6 : usb-storage 2-2:1.0
[19343.615795] input: LaCie d2 quadra (button) as /devices/pci0000:00/0000:00:1d.7/usb2/2-2/2-2:1.1/input/input13
[19343.615989] generic-usb 0003:059F:1014.0003: input,hidraw0: USB HID v1.11 Device [LaCie d2 quadra (button)] on usb-0
000:00:1d.7-2/input1
[19344.610282] scsi 6:0:0:0: Direct-Access LaCie d2 quadra PQ: 0 ANSI: 4
[19344.612000] sd 6:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[19344.612894] sd 6:0:0:0: [sdb] Write Protect is off
[19344.612897] sd 6:0:0:0: [sdb] Mode Sense: 10 00 00 00
[19344.613910] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[19344.618146] sdb: sdb1
[19344.627243] sd 6:0:0:0: [sdb] Attached SCSI disk
___________________________
but I cannot mount it. when i try i get the error that xfs is an unknown file system type.
and no, there is nothing in errors.log or anyplace else i've checked.
it seems weird to me too...
Last edited by djg1971 (2011-11-21 21:13:09)
Offline
Been a while since I messed with xfs. Try this:
# mount -t xfs /dev/sdxy /path/to/mountpoint
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
xfsprogs was updated sometime recently. I tried before and after the update though, and didn't have any problems.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
graysky:
I tried issuing the command directly ("mount -t ........") also, before posting. The result is the same error - mount doesn't know about xfs.
Offline
First, run lsmod | grep xfs to see if the module is loaded. If you don't see something like
xfs 742285 0
then run (as root) modprobe xfs .
If it doesn't return an error, try mounting again afterwards.
Last edited by alphaniner (2011-11-21 21:50:26)
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
alphaniner:
That I didn't try. The result is not good:
"FATAL: Module xfs not found."
I must have all the necessary packages installed as this was working when I went out of town last Monday night. Any idea where to go from here?
Offline
Are you using a custom kernel or something? For me, the xfs module came with the kernel package (linux):
$ pacman -Ql |grep xfs.ko.gz
linux /lib/modules/3.1.1-1-ARCH/kernel/fs/xfs/xfs.ko.gz
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
No custom kernel. Here is the output from the command:
[root@xxxxx log]# pacman -Ql |grep xfs.ko.gz
linux /lib/modules/3.1.1-1-ARCH/kernel/fs/xfs/xfs.ko.gz
Offline
Reboot, you probably upgraded to a more recent kernel, so that the kernel you are using does not find the newer modules
Mortuus in anima, curam gero cutis
Offline
Agree with patroclo, that seems the likely explanation. uname -r should give you
3.1.1-1-ARCH
If not you are running a different kernel than what's currently installed
Offline
okay ... i'm officially embarrassed. I was extremely busy this morning after returning from a field experiment and forgot that the kernel was updated during the system upgrade I did, so had not rebooted. I am indeed using the latest kernel, and rebooting did indeed solve the problem. Thanks, and sorry for wasting your time to everyone who tried to help.
Offline
okay ... i'm officially embarrassed. [...] Thanks, and sorry for wasting your time to everyone who tried to help.
Hi. Don't be embarrassed. I got the same problem, but with iso 9660. This thread just saved me some time I'm going to reboot right now.
Offline