XFS uses 64-bit inodes being mounted without inode64 option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
After upgrade from 12.04 XFS became to use 64bit inodes, despite the fact that it is mounted without inode64 option:
root@nfs:~# mount | grep /raid
/dev/sdb1 on /raid type xfs (rw,noatime,
Volume size is 11TB that is much less than 16TB limit for 32bit inodes:
root@nfs:~# df -h /raid
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 11T 3,3T 7,7T 31% /raid
But there are files wih 64bit inodes on this volume, e.g.:
root@nfs:~# stat /raid/home/nz/.ssh
File: ‘/raid/
Size: 122 Blocks: 0 IO Block: 5242880 directory
Device: 811h/2065d Inode: 25788470353 Links: 2
Access: (0700/drwx------) Uid: (30051/nz) Gid: ( 513/Domain Users)
Access: 2014-08-22 17:13:25.804584309 +0400
Modify: 2014-08-25 10:29:02.582411181 +0400
Change: 2014-08-25 10:29:02.582411181 +0400
Birth: -
All such files are created after 12.04 -> 14.04 upgrade.
There is a plenty of 32-bit old software that could not access files with 64-bit inodes, and it seems that the only option is to recreate the whole volume with ext4 filesystem instead of xfs.
root@nfs:~# lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 авг. 22 09:45 seq
crw-rw---- 1 root audio 116, 33 авг. 22 09:45 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2014-04-18 (130 days ago)
InstallationMedia: Ubuntu-Server 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
Lsusb:
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Supermicro X8SIE
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.127.5
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-34-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-08-16 (10 days ago)
UserGroups: Account Operators Administrators Domain Admins
WifiSyslog:
_MarkForUpload: True
dmi.bios.date: 05/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0c
dmi.board.
dmi.board.name: X8SIE
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.
dmi.chassis.type: 24
dmi.chassis.vendor: Supermicro
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: X8SIE
dmi.product.
dmi.sys.vendor: Supermicro
affects: | ubuntu → linux (Ubuntu) |
tags: | added: kernel-bug-exists-upstream |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1361637/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]