public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Jan de Kruyf <jan.de.kruyf@gmail.com>, xfs@oss.sgi.com
Subject: Re: Data loss XFS with RT kernel on Debian.
Date: Sat, 05 Jul 2014 15:06:08 -0500	[thread overview]
Message-ID: <53B85AB0.30800@sandeen.net> (raw)
In-Reply-To: <CAA85NCjXU7rK8C4AcQ4Tnxowx5MFBUyAoLW_nuwmKyOFL-_PgQ@mail.gmail.com>

On 7/5/14, 7:41 AM, Jan de Kruyf wrote:
> Hallo,
> 
> While doing a reasonably high density job like rsynching a subdirectory from one place to another, or tarring it to a pipe and untarring it at the other end, I note that the cpu usage goes practically to 100% and when I after 5 minutes or so I reset the computer the writing has not finished at all.
> However on the stock Debian kernel it works without a problem.
> 
> Could I still use this combination in an industrial environment reading and writing reasonably short text files? So far I did not experience this problem with normal day to day use. It stuck up its head during installation of   gnat-gpl-2014-x86_64-linux-bin from the http://libre.adacore.com/download/ page. The offending code is in the Makefile in the top directory page. The Xterm will give you the place where it gets stuck.

http://lwn.net/Articles/457667/

-Eric

> Regards,
> 
> Jan de Kruijf.
> 
> 
> Her are the details of the installation:
> 
> root@jan:~# xfs_info -V
> xfs_info version 3.1.7
> 
> root@jan:~# xfs_info /usr
> meta-data=/dev/sda3 isize=256 agcount=4, agsize=732416 blks
>               = sectsz=512 attr=2
>        data = bsize=4096 blocks=2929664, imaxpct=25
>                = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=2560, version=2
>        = sectsz=512 sunit=0 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
> 
> This combination does not work:
> root@jan:~# uname -a
> Linux jan 3.14-0.bpo.1-rt-amd64 #1 SMP PREEMPT RT Debian 3.14.7-1~bpo70+1 (2014-06-21) x86_64 GNU/Linux
> 
> Also kernel 3.10-0.bpo.3-rt-amd64 does not work
> 
> But this combination works:
>  root@jan:~# uname -a
> Linux jan 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

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

  reply	other threads:[~2014-07-05 20:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 12:41 Data loss XFS with RT kernel on Debian Jan de Kruyf
2014-07-05 20:06 ` Eric Sandeen [this message]
2014-07-05 22:08   ` Eric Sandeen
2014-07-06 23:57 ` Dave Chinner
2014-07-07  7:59   ` Jan de Kruyf
2014-07-07  9:43     ` Dave Chinner
  -- strict thread matches above, loose matches on Subject: below --
2014-07-07 10:39 Jan de Kruyf

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=53B85AB0.30800@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=jan.de.kruyf@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