From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9fans@9fans.net
Subject: [9fans] atagenioretry: nondma
Date: Sun, 19 May 2013 13:32:52 +0900 [thread overview]
Message-ID: <5F4ED75F-A4FB-4B81-9595-24D2A06A4E24@ar.aichi-u.ac.jp> (raw)
Hello,
yesterday day I had error messages below:
automatic dump Fri May 17 05:00:07 2013
automatic dump Sat May 18 05:00:08 2013
command 30
data f7aea8a0 limit f7aec0a0 dlen 16384 status 0 error 0
lba 163565804 -> 163565804, count 32 -> 32 (32)
atagenioretry: nondma w:163565804:32 @163565804:32
wrenwrite: error on w"/dev/sdD0/fsworm"(2315949): i/o error 040804 163565804
mirrwrite: error at w"/dev/sdD0/fsworm" block 2315949
atagenioretry: nondma w:163565836:32 @163565836:32
wrenwrite: error on w"/dev/sdD0/fsworm"(2315950): i/o error 040804 163565836
mirrwrite: error at w"/dev/sdD0/fsworm" block 2315950
atagenioretry: nondma w:163565900:32 @163565900:32
wrenwrite: error on w"/dev/sdD0/fsworm"(2315952): i/o error 040804 163565900
mirrwrite: error at w"/dev/sdD0/fsworm" block 2315952
atagenioretry: nondma w:163565932:32 @163565932:32
...
...
it seems that wrenwrite/mirrwrite errors from cwfs are induced by "atagenioretry: nondma"
which come from kernel (/sys/src/9/pc/sdide.c).
have you ever seen messages like this?
I suspected my sata drive (/dev/sdD0) has broken. but it seems the drive is alive.
Kenji Arisawa
next reply other threads:[~2013-05-19 4:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 4:32 arisawa [this message]
2013-05-19 14:13 ` erik quanstrom
2013-05-19 15:55 ` cinap_lenrek
2013-05-19 17:47 ` erik quanstrom
2013-05-19 17:52 ` erik quanstrom
2013-05-20 22:10 ` arisawa
2013-05-21 1:40 ` erik quanstrom
2013-05-22 23:18 ` arisawa
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=5F4ED75F-A4FB-4B81-9595-24D2A06A4E24@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).