op 24-03-14 18:36, Dave Chinner
We currently have the following options in fstab for the filesystem:
On Mon, Mar 24, 2014 at 10:24:45AM +0100, Michel Verbraak(1st-Setup) wrote:
We have a problem with one of our systems which is using XFS but we are
unable to find the problem. Recently we had two moments, Tuesday 4th of
March and Friday the 21st of March, where we had to reboot the system to
get it up and running again.
- The programs handling files on the XFS disc stop working when
creating, deleting or writing files. They do not error they are just
waiting on the command to complete.
- One of our programs, a java application, goes into very high cpu usage
(50%) which normally is at 1%. This could be something in our java
application but it happens at the moment handling files gets stuck.
- A nice restart of the programs does not succeed as wel a kill -9 does
- Trying to reboot the servers in a normal fashion does not work. As it
is a virtual machine we have to do a shutdown (unplug power) and start
it up again to get it up and running.
Following details I have for you:
System OS: Ubuntu 12.04 LTS
Kernel: 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Server: Virtual machine in a VMWare setup.
Disc: 300GB direct attached LUN
We have an exact clone of this system for our acceptance environment. In
this environment we are unable to reproduce this problem/situation.
Differences between the two days is that our services on 2014-03-21 were
quit busy with a lot of file changes on the xfs disc and on 2014-03-04
the system was very quiet on the moment the kernel traces appear and the
services get stuck.
Any help is appreciated.
Regards Michel Verbraak.
Following we see in the syslog on both moments (2014-03-04 and 2014-03-21):
Mar 21 06:32:20 ealxs00169 kernel: [1412280.930543] flush-8:16 D
0000000000000000 0 13864 2 0x00000000
[<ffffffffa007980d>] xfs_vm_writepages+0x4d/0x60 [xfs]
Writeback is blocked on a locked page, and is waiting for IO
Now I read everywhere to turn of barrier you should specify
"nobarrier". Is our way of disabling wrong?
The disc used has "write cache" disabled:
[ 2.875792] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 2.876376] sd 3:0:0:0: [sdb] 629145600 512-byte logical blocks:
(322 GB/300 GiB)
[ 2.876879] sd 3:0:0:0: [sdb] Write Protect is off
[ 2.877050] sd 3:0:0:0: [sdb] Mode Sense: 87 00 00 08
[ 2.877890] sd 3:0:0:0: [sdb] Write cache: disabled, read cache:
enabled, doesn't support DPO or FUA
[ 2.885634] sdb: unknown partition table
[ 5.132308] SGI XFS with ACLs, security attributes, realtime,
large block/inode numbers, no debug enabled
[ 5.155268] SGI XFS Quota Management subsystem
[ 5.159345] XFS (sdb): Mounting Filesystem
Following is output of xfs_info on sdb:
meta-data="" isize=256 agcount=4,
= sectsz=512 attr=2
data = bsize=4096 blocks=78643200,
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=38400,
= sectsz=512 sunit=0 blks,
realtime =none extsz=4096 blocks=0, rtextents=0
Mar 21 06:34:20 ealxs00169 kernel: [1412400.891181] archiver.pl D