linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Emmanuel Florac <eflorac@intellique.com>,
	Rotem Ben Arye <rotem.benarye@gmail.com>,
	xfs@oss.sgi.com
Subject: Re: XFS File System Monitor
Date: Fri, 03 Jan 2014 12:24:54 -0600	[thread overview]
Message-ID: <52C70076.3090004@sandeen.net> (raw)
In-Reply-To: <20140102142755.3659bd42@harpe.intellique.com>

On 1/2/14, 7:27 AM, Emmanuel Florac wrote:
> Le Thu, 2 Jan 2014 15:20:58 +0200
> Rotem Ben Arye <rotem.benarye@gmail.com> écrivait:
> 
>> HI , I'm not sure it will help here,  we  are working central storage
>> with Netapp , EMC and others ,
>> The Using of XFS File system on volume , is expressed with an
>> creation of XFS, as e.g :  mkfs.xfs.
>>  My question about what are the tools that could assist us to monitor
>> XFS file system was in general.
> 
> Rotem, if you have no SGI supported hardware, SGI support won't help
> you.
> 
> Furthermore, it's impossible to help you without more details: what is
> the hardware setup, the exact OS version and linux kernel in use.
> 

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-01-03 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 13:04 XFS File System Monitor support
2014-01-02 13:20 ` Rotem Ben Arye
2014-01-02 13:27   ` Emmanuel Florac
2014-01-03 18:24     ` Eric Sandeen [this message]
2014-01-04  7:27       ` Rotem Ben Arye
  -- strict thread matches above, loose matches on Subject: below --
2014-01-02 12:16 Rotem Ben Arye
2014-01-02 15:07 ` Stan Hoeppner
     [not found]   ` <CA+apj_iOy2dqyPGunKe91WLCqy71uE1uq2HZQ_v=+QHewCymeA@mail.gmail.com>
2014-01-04 15:45     ` Stan Hoeppner

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=52C70076.3090004@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=eflorac@intellique.com \
    --cc=rotem.benarye@gmail.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 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).