public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
Date: Tue, 26 Oct 2010 09:24:57 +0200	[thread overview]
Message-ID: <4CC68249.7050409@profihost.ag> (raw)
In-Reply-To: <20101026092205.086c0d89@galadriel.home>

Am 26.10.2010 09:22, schrieb Emmanuel Florac:
> xfs_info /dev/sdc3

Hi here are the details:

root@server361-han:~# xfs_info /dev/sdc3

meta-data=/dev/sdc3              isize=256    agcount=32, 
agsize=40038461 blks
          =                       sectsz=512   attr=0
data     =                       bsize=4096   blocks=1281230752, imaxpct=25
          =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096
log      =internal               bsize=4096   blocks=32768, version=2
          =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

root@server361-han:~# mount|grep sdc3

/dev/sdc3 on /sdc3 type xfs (rw,noatime,nodiratime,nobarrier,prjquota)
/sdc3/serverbackup on /serverbackup type none (rw,bind)
/sdc3/serverbackup_rootserver on /serverbackup_rootserver type none 
(rw,bind)

Stefan

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

  reply	other threads:[~2010-10-26  7:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  6:25 Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1 Stefan Priebe - Profihost AG
2010-10-26  7:22 ` Emmanuel Florac
2010-10-26  7:24   ` Stefan Priebe - Profihost AG [this message]
2010-10-26  7:41     ` Emmanuel Florac
2010-10-26  7:53       ` Stefan Priebe - Profihost AG
2010-10-26 11:01         ` Emmanuel Florac
2010-10-26 11:03           ` Stefan Priebe - Profihost AG
2010-10-26 11:25             ` Emmanuel Florac
2010-10-26 12:09               ` Stefan Priebe - Profihost AG
2010-10-26 13:00                 ` Emmanuel Florac
2010-10-26 23:23               ` Michael Monnerie
2010-10-27  3:55                 ` Dave Chinner
2010-10-27 10:58                   ` Michael Monnerie
2010-10-27 20:59                     ` Dave Chinner
2010-10-28  9:39                       ` Michael Monnerie
2010-10-27  6:04                 ` Emmanuel Florac
2010-10-27  7:00                   ` Stefan Priebe - Profihost AG
2010-10-27 10:06                     ` Emmanuel Florac
2010-10-27 10:08                       ` Stefan Priebe - Profihost AG
2010-10-27 10:12                         ` Emmanuel Florac
2010-10-27 10:22                           ` Stefan Priebe - Profihost AG
2010-10-27 11:14                             ` Emmanuel Florac
2010-10-26 11:30             ` Larsen, Tore Høivaag
2010-10-26 11:47               ` Emmanuel Florac
2010-11-01  8:01     ` Stefan Priebe - Profihost AG
2010-11-01 10:11       ` Emmanuel Florac
2010-11-01 10:28         ` Stefan Priebe - Profihost AG
2010-11-01 12:27       ` Dave Chinner
2010-11-01 12:28         ` Stefan Priebe - Profihost AG
2010-11-01 12:52           ` Dave Chinner
2010-11-01 13:29           ` Emmanuel Florac
2010-11-01 13:48             ` Stefan Priebe - Profihost AG

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=4CC68249.7050409@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=eflorac@intellique.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