From: xfs@bob.dscon.sk (DS)
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: kernel 2.6.27.7 problem
Date: Sat, 6 Dec 2008 14:20:26 +0100 [thread overview]
Message-ID: <20081206132026.GA24765@bob.dscon.sk> (raw)
In-Reply-To: <alpine.DEB.1.10.0812060713010.8516@p34.internal.lan>
iSCSI storage is nexsan SATA boy with 2 controlers, firmware was updated
few months ago
other 3 servers has data on this storage without problems (all on XFS)
all is going on same switch, all ports are in one storage VLAN
I don't know where "start debug" and it must be safe for data.
Dusan
On Sat, Dec 06, 2008 at 07:13:22AM -0500, Justin Piszcz wrote:
>
>
> On Sat, 6 Dec 2008, Justin Piszcz wrote:
>
> >
> >
> >On Sat, 6 Dec 2008, DS wrote:
> >
> >>No other messages before. No iSCSI/network messages...nothing.
> >>Only this few lines and FS is down. After remount it works ....while and
> >>hangs again.
> >>Few hours it runs back on 2.6.24.3 and everything is OK.
> >>
> >>It's production system, but I test it again in late night.
> >>What can I do to identify problem?
> >>
> >>Dusan
> >
> >Run:
> >smartctl -a /dev/sde
> >
> >Post output.
> >
> >Justin.
> >
> >
>
> AMD x64, debian stable (etch)
> filesytem is on iSCSI storage
> ^^^^^^^^^^^^^^
>
> Nevermind my comment above:
>
> Is there anyway to test the health of the disks on the system?
>
> Justin.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-06 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 2:36 kernel 2.6.27.7 problem DS
2008-12-06 3:27 ` 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 [this message]
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=20081206132026.GA24765@bob.dscon.sk \
--to=xfs@bob.dscon.sk \
--cc=jpiszcz@lucidpixels.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.