From: Eric Chamberland <Eric.Chamberland@giref.ulaval.ca>
To: Thomas Rast <trast@student.ethz.ch>
Cc: "Brian J. Murrell" <brian@interlinx.bc.ca>,
git@vger.kernel.org, kusmabite@gmail.com, "Pyeron,
Jason J CTR (US)" <jason.j.pyeron.ctr@mail.mil>,
"Maxime Boissonneault" <maxime.boissonneault@calculquebec.ca>,
"Philippe Vaucher" <philippe.vaucher@gmail.com>,
"Sébastien Boisvert" <sebastien.boisvert@calculquebec.ca>
Subject: Re: GIT get corrupted on lustre
Date: Tue, 22 Jan 2013 17:46:08 -0500 [thread overview]
Message-ID: <50FF16B0.8010206@giref.ulaval.ca> (raw)
In-Reply-To: <878v7keuh3.fsf@pctrast.inf.ethz.ch>
On 01/22/2013 05:14 PM, Thomas Rast wrote:
> Eric Chamberland <Eric.Chamberland@giref.ulaval.ca> writes:
>
>> So, hum, do we have some sort of conclusion?
>>
>> Shall it be a fix for git to get around that lustre "behavior"?
>>
>> If something can be done in git it would be great: it is a *lot*
>> easier to change git than the lustre filesystem software for a cluster
>> in running in production mode... (words from cluster team) :-/
>
> I thought you already established that simply disabling the progress
> display is a sufficient workaround? If that doesn't help, you can try
> patching out all use of SIGALRM within git.
>
I tried that solution after Brian told me to try it, but it didn't
solved the problem for me! :-(
> Other than that I agree with Junio, from what we've seen so far, Lustre
> returns EINTR on all sorts of calls that simply aren't allowed to do so.
>
Ok, so now the "good" move would be to have all this reported to lustre
development team? Brian, have you seen anything new from what you have
already reported? I have to admit that I am not a fs expert...
And I also agree with Junio point of view: The problem may impact
mission critical applications....
Eric
next prev parent reply other threads:[~2013-01-22 22:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 14:08 GIT get corrupted on lustre Eric Chamberland
2012-12-24 14:48 ` Andreas Schwab
2012-12-24 15:11 ` Brian J. Murrell
2013-01-08 16:11 ` Eric Chamberland
2013-01-09 21:20 ` Eric Chamberland
2013-01-17 13:07 ` Eric Chamberland
2013-01-17 14:23 ` Philippe Vaucher
2013-01-17 16:30 ` Eric Chamberland
2013-01-17 16:40 ` Pyeron, Jason J CTR (US)
2013-01-17 16:41 ` Maxime Boissonneault
2013-01-17 17:17 ` Pyeron, Jason J CTR (US)
2013-01-18 17:50 ` Eric Chamberland
2013-01-21 13:29 ` Erik Faye-Lund
2013-01-21 16:11 ` Thomas Rast
2013-01-21 16:14 ` Maxime Boissonneault
2013-01-21 16:20 ` Thomas Rast
2013-01-21 18:54 ` Brian J. Murrell
2013-01-21 19:29 ` Thomas Rast
2013-01-22 21:31 ` Eric Chamberland
2013-01-22 22:03 ` Junio C Hamano
2013-01-22 22:14 ` Thomas Rast
2013-01-22 22:46 ` Eric Chamberland [this message]
2013-01-23 14:45 ` Sébastien Boisvert
2013-01-23 14:50 ` Sébastien Boisvert
2013-01-23 15:23 ` Erik Faye-Lund
2013-01-23 15:32 ` Thomas Rast
2013-01-23 15:32 ` Erik Faye-Lund
2013-01-23 15:44 ` Thomas Rast
2013-01-23 15:54 ` Erik Faye-Lund
2013-01-23 17:23 ` Jonathan Nieder
2013-01-23 18:34 ` Sébastien Boisvert
2013-02-04 13:58 ` Eric Chamberland
2013-01-21 17:07 ` Eric Chamberland
2013-01-21 18:28 ` Eric Chamberland
2012-12-25 1:11 ` Greg Troxel
2012-12-26 22:51 ` Jeff King
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=50FF16B0.8010206@giref.ulaval.ca \
--to=eric.chamberland@giref.ulaval.ca \
--cc=brian@interlinx.bc.ca \
--cc=git@vger.kernel.org \
--cc=jason.j.pyeron.ctr@mail.mil \
--cc=kusmabite@gmail.com \
--cc=maxime.boissonneault@calculquebec.ca \
--cc=philippe.vaucher@gmail.com \
--cc=sebastien.boisvert@calculquebec.ca \
--cc=trast@student.ethz.ch \
/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).