All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Sagar Borikar <Sagar_Borikar@pmc-sierra.com>
Cc: Dave Chinner <david@fromorbit.com>,
	Nathan Scott <nscott@aconex.com>,
	xfs@oss.sgi.com
Subject: Re: Xfs Access to block zero  exception and system crash
Date: Sat, 05 Jul 2008 11:25:57 -0500	[thread overview]
Message-ID: <486FA095.1050106@sandeen.net> (raw)
In-Reply-To: <340C71CD25A7EB49BFA81AE8C839266702997658@BBY1EXM10.pmc_nt.nt.pmc-sierra.bc.ca>

Sagar Borikar wrote:
> Copy is of the same file to 30 different directories and it is basically
> overwrite.
> 
> Here is the setup:
> 
> It's a JBOD with Volume size 20 GB. The directories are empty and this
> is basically continuous copy of the file on all thirty directories. But
> surprisingly none of the copy succeeds. All the copy processes are in 
> Uninterruptible sleep state and xfs_repair log I have already attached 
> With the prep. As mentioned it is with 2.6.24 Fedora kernel.

It would probably be best to try a 2.6.26 kernel from rawhide to be sure
you're closest to the bleeding edge.

I tested on 2.6.24.7-92.fc8 on x86_64, and I did this, specifically, in
the root of a 30G xfs fs:

# for I in `seq 1 30`; do mkdir dir$I; done
# vi copyit.sh (your script)
# chmod +x copyit.sh
# dd if=/dev/zero of=300mbfile bs=1M count=300
# for I in `seq 1 30`; do ./copyit.sh 300mbfile dir$I & done

I got no errors or corruption after several iterations.

Might also be worth checking dmesg for any errors when you run.

-Eric

  reply	other threads:[~2008-07-05 16:25 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24  7:03 Xfs Access to block zero exception and system crash Sagar Borikar
2008-06-25  6:48 ` Sagar Borikar
2008-06-25  8:49 ` Dave Chinner
2008-06-26  6:46   ` Sagar Borikar
2008-06-26  7:02     ` Dave Chinner
2008-06-27 10:13       ` Sagar Borikar
2008-06-27 10:25         ` Sagar Borikar
2008-06-28  0:05           ` Dave Chinner
2008-06-28 16:47             ` Sagar Borikar
2008-06-29 21:56               ` Dave Chinner
2008-06-30  3:37                 ` Sagar Borikar
     [not found]                 ` <20080630034112.055CF18904C4@bby1mta01.pmc-sierra.bc.ca>
2008-06-30  6:07                   ` Sagar Borikar
2008-06-30 10:24                   ` Sagar Borikar
2008-07-01  6:44                     ` Dave Chinner
2008-07-02  4:18                       ` Sagar Borikar
2008-07-02  5:13                         ` Dave Chinner
2008-07-02  5:35                           ` Sagar Borikar
2008-07-02  6:13                             ` Nathan Scott
2008-07-02  6:56                               ` Dave Chinner
2008-07-02 11:02                                 ` Sagar Borikar
2008-07-03  4:03                                   ` Eric Sandeen
2008-07-03  5:14                                     ` Sagar Borikar
2008-07-03 15:02                                       ` Eric Sandeen
2008-07-04 10:18                                         ` Sagar Borikar
2008-07-04 12:27                                           ` Dave Chinner
2008-07-04 17:30                                             ` Sagar Borikar
2008-07-04 17:35                                               ` Eric Sandeen
2008-07-04 17:51                                                 ` Sagar Borikar
2008-07-05 16:25                                                   ` Eric Sandeen [this message]
2008-07-06 17:24                                                     ` Sagar Borikar
2008-07-06 19:07                                                       ` Eric Sandeen
2008-07-07  3:02                                                         ` Sagar Borikar
2008-07-07  3:04                                                           ` Eric Sandeen
2008-07-07  3:07                                                             ` Sagar Borikar
2008-07-07  3:11                                                               ` Eric Sandeen
2008-07-07  3:17                                                                 ` Sagar Borikar
2008-07-07  3:22                                                                   ` Eric Sandeen
2008-07-07  3:42                                                                     ` Sagar Borikar
     [not found]                                                                       ` <487191C2.6090803@sandeen  .net>
     [not found]                                                                         ` <4871947D.2090701@pmc-sierr a.com>
2008-07-07  3:47                                                                       ` Eric Sandeen
2008-07-07  3:58                                                                         ` Sagar Borikar
2008-07-07  5:19                                                                           ` Eric Sandeen
2008-07-07  5:58                                                                             ` Sagar Borikar
2008-07-06  4:19                                                   ` Dave Chinner
2008-07-04 15:33                                           ` Eric Sandeen
2008-06-28  0:02         ` Dave Chinner
     [not found] <4872E0BC.6070400@pmc-sierra.com>
     [not found] ` <4872E33E.3090107@sandeen.net>
2008-07-08  5:03   ` Sagar Borikar
2008-07-09 16:57   ` Sagar Borikar
2008-07-10  5:12     ` Sagar Borikar

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=486FA095.1050106@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=Sagar_Borikar@pmc-sierra.com \
    --cc=david@fromorbit.com \
    --cc=nscott@aconex.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.