From: xfs@bob.dscon.sk (DS)
To: xfs@oss.sgi.com
Subject: kernel 2.6.27.7 problem
Date: Sat, 6 Dec 2008 03:36:09 +0100 [thread overview]
Message-ID: <20081206023608.GA22135@bob.dscon.sk> (raw)
Hi,
I have trouble with xfs after upgrade kernel 2.6.24.3 -> 2.6.27.7.
Message on console:
end_request: I/O error, dev sde, sector 351572544
I/O error in filesystem ("sde1") meta-data dev sde1 block 0x14f49201
("xlog_iodone") error 5 buf count 9728
xfs_force_shutdown(sde1,0x2) called from line 1056 of file
fs/xfs/xfs_log.c. Return address = 0xffffffff80373233
Filesystem "sde1": Log I/O Error Detected. Shutting down filesystem:
sde1
Please umount the filesystem, and rectify the problem(s)
Remount is possible, but filesystem hangs up again.
After xfs_repair too.
It looks OK now after rebooting to old kernel.
On other similar system (same disk array, other vol) I use 2.6.27.6 kernel without problems.
System:
AMD x64, debian stable (etch)
filesytem is on iSCSI storage
mount options:
rw,noatime,nodiratime,logbsize=256k,logbufs=8,quota
xfs_info:
meta-data=/dev/sde1 isize=256 agcount=16, agsize=5493104
blks
= sectsz=512 attr=0
data = bsize=4096 blocks=87889584,
imaxpct=25
= sunit=16 swidth=112 blks
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=65536 blocks=0, rtextents=0
Any ideas.
Thanx
Dusan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2008-12-06 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 2:36 DS [this message]
2008-12-06 3:27 ` kernel 2.6.27.7 problem Eric Sandeen
2008-12-06 9:10 ` DS
2008-12-06 12:12 ` Justin Piszcz
2008-12-06 12:13 ` Justin Piszcz
2008-12-06 13:20 ` DS
2008-12-06 13:42 ` Eric Sandeen
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=20081206023608.GA22135@bob.dscon.sk \
--to=xfs@bob.dscon.sk \
--cc=xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox