All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: "E.Gryaznova" <grev@namesys.com>, Vitaly Fertman <vitaly@namesys.com>
Cc: scott <scottfk@yahoo.com>, reiserfs-list@namesys.com
Subject: Re: hard hang with reiser4-for-2.6.11-5 and VMware Workstation 5.0
Date: Fri, 17 Jun 2005 11:38:03 -0700	[thread overview]
Message-ID: <42B3188B.2010103@namesys.com> (raw)
In-Reply-To: <42B308C0.4050807@namesys.com>

E.Gryaznova wrote:

> Hello.
>
> Thank you for the report.
>
> VMWare/reiser4 is known problem, we can reproduce it.  But
> unfortunately I can't  estimate when this will be fixed.
> Reiser4 format was changed in reiser4-5 patch for 2.6.11, reiser4progs
> for this format are not ready yet.
>
> Thanks,
> Lena
>
> scott wrote:
>
>> Greetings,
>>
>> I have been using Reiser4 as my primary filesystem for
>> some time now, and for the first time have encountered
>> a problem that keeps me from doing what I want to do.
>>
>> I run VMware Workstation 5.0 with the virtual disk
>> files on my Reiser4 / partition, which happens to be a
>> Linux md RAID1 device.  The other day I built a new
>> kernel, upgrading to the -5 release of the reiser4
>> patches.  Either during boot or shortly after boot of
>> any guest OS, my workstation becomes totally
>> unresponsive.  Magic SysRq keys don't even work.
>>  
>>
>
>> To narrow down the source of the problem, I applied
>> the Reiser4 patch to a vanilla 2.6.11 kernel tree.  I
>> saw the exact same issue.
>>
>> I tried reverting to a previous version of the Reiser4
>> patch, but I get VFS errors about being unable to find
>> a Reiser4 filesystem on my rootdisk using any other
>> Reiser4 patchset.  Did the filesystem format change?
>>  
>>
>
>> I tried recompiling the -5 release with debug enabled,
>> but since the machine is unresponsive, I don't see any
>> output.
>>
>> My question...  is this a known issue?  Or should I
>> just keep pounding away at this until I can get some
>> sort of debugging information?
>>
>> Thanks to you all for the always-interesting
>> discussion threads on this list.  And thanks, Hans,
>> for reiserfs and reiser4.
>>
>> be seeing you.
>>
>> scott
>>
>>
>>        
>> ____________________________________________________ Yahoo! Sports
>> Rekindle the Rivalries. Sign up for Fantasy Football
>> http://football.fantasysports.yahoo.com
>>
>>
>>  
>>
>
>
>
>
Vitaly, what is the eta on updating reiser4progs?

  parent reply	other threads:[~2005-06-17 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17 17:05 hard hang with reiser4-for-2.6.11-5 and VMware Workstation 5.0 scott
2005-06-17 17:30 ` E.Gryaznova
2005-06-17 17:49   ` Wil Reichert
2005-06-17 17:54     ` scott
2005-06-17 18:11       ` Wil Reichert
2005-06-17 18:27         ` scott
2005-06-17 18:38   ` Hans Reiser [this message]
2005-06-18 10:29   ` mjt
2005-06-18 13:56     ` Vitaly Fertman
2005-06-18 14:36       ` mjt
2005-06-20 11:36         ` Vladimir Saveliev
2005-06-20 12:24           ` mjt
2005-06-20 12:34             ` Francesco Biscani
2005-06-20 16:18             ` Vladimir Saveliev
2005-06-21 17:56               ` mjt

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=42B3188B.2010103@namesys.com \
    --to=reiser@namesys.com \
    --cc=grev@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=scottfk@yahoo.com \
    --cc=vitaly@namesys.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.