public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Geir A. Myrestrand" <geir.myrestrand@falconstor.com>
To: xfs@oss.sgi.com
Cc: Eric Sandeen <sandeen@sandeen.net>, nscott@aconex.com
Subject: Re: New CentOS4/RHEL4-compatible xfs module rpms
Date: Thu, 07 Dec 2006 18:08:04 -0500	[thread overview]
Message-ID: <45789ED4.5000203@falconstor.com> (raw)
In-Reply-To: <45789B83.5010800@sandeen.net>

Eric Sandeen wrote:
> 
> You don't have multiple concurrent freezes happening do you....
> 
> -Eric
> 

Nope, I don't need to. Now it happens on the first call to xfs_freeze. 
Sometimes in the past I did freeze, unfreeze, and then freeze before it 
happened, but this was still serialized from the same terminal window.

Oh, could strace be the reason as to why it now always happens on the 
first invocation of the freeze command? Maybe it affects the wait 
calls... Well, without strace it would probably just happen on the 
second invocation of freeze (after unfreeze) like it did on RHELAS4U2...

My test case is very simple, the only thing special is that I simplified 
my test case so much that I end up using a file as my disk (setup as a 
loopback device). However, the problem was initially discovered using a 
real disk, so I don't think that is the problem.

If you're interested I can forward the test case involving probably less 
than 10 commands and a simple Perl script of maybe 20 lines.

-- 

Geir A. Myrestrand

  reply	other threads:[~2006-12-07 23:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 19:07 New CentOS4/RHEL4-compatible xfs module rpms Eric Sandeen
2006-12-07 17:25 ` Geir A. Myrestrand
2006-12-07 17:52   ` Eric Sandeen
2006-12-07 18:17     ` Geir A. Myrestrand
2006-12-07 23:26       ` David Chinner
2006-12-08  2:58         ` Geir A. Myrestrand
2006-12-07 18:19     ` Geir A. Myrestrand
2006-12-07 20:51     ` Geir A. Myrestrand
2006-12-07 21:11       ` Nathan Scott
2006-12-07 21:35         ` Geir A. Myrestrand
2006-12-07 21:40           ` Nathan Scott
2006-12-07 21:51             ` Geir A. Myrestrand
2006-12-07 22:06               ` Nathan Scott
2006-12-07 22:16                 ` Geir A. Myrestrand
2006-12-07 22:18                   ` Eric Sandeen
2006-12-07 22:25                     ` Geir A. Myrestrand
2006-12-07 22:30                       ` Eric Sandeen
2006-12-07 22:52                         ` Geir A. Myrestrand
2006-12-07 22:53                           ` Eric Sandeen
2006-12-07 23:08                             ` Geir A. Myrestrand [this message]
2007-07-19 14:37 ` James Braid
2007-07-19 15:15   ` Eric Sandeen
2007-07-21  3:34     ` James Braid
2007-07-21 14:58       ` Eric Sandeen
2007-07-21 15:36         ` James Braid
  -- strict thread matches above, loose matches on Subject: below --
2007-08-08 16:04 James Pearson
2007-08-08 16:09 ` Eric Sandeen

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=45789ED4.5000203@falconstor.com \
    --to=geir.myrestrand@falconstor.com \
    --cc=nscott@aconex.com \
    --cc=sandeen@sandeen.net \
    --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