All of lore.kernel.org
 help / color / mirror / Atom feed
From: Szabolcs Illes <illes@cpc.wmin.ac.uk>
To: Alex Zarochentsev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 bug
Date: Fri, 04 Mar 2005 14:38:32 +0000	[thread overview]
Message-ID: <422872E8.4020301@cpc.wmin.ac.uk> (raw)
In-Reply-To: <20050304134843.GK6393@backtop.namesys.com>

Alex Zarochentsev wrote:

>Hello,
>
>On Sun, Feb 27, 2005 at 07:34:11PM +0000, Szabolcs Illes wrote:
>  
>
>>Hi All,
>>
>>I have been using reiser4fs for 4 months without any problem since 
>>today. After tryinig to open a movie with mplayer a have this in my log:
>>    
>>
>
>how large was the movie file?
>
It was about 300MB. But previously I have copied a lot of relative big 
movies (600-700 MB).

>  We have another similar bug report related to
>writing/reading of a large (20GB) tar file, so file size may be important.
>  
>
I think the larges file I have ever stored using reiser4 was about 3 or 
4 GB. ( for example: vmware disk images, dvd isos ...)

>  
>
>>Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: 
>>write_sd_by_inode_common (fs/reiser4/plugin/object.c:480)[nikita-2221]:
>>Feb 27 14:00:22 sunset kernel: WARNING: Failed to save sd for 1599330: -5
>>Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: create_child_common 
>>(fs/reiser4/plugin/dir/dir.c:501)[nikita-2219]:
>>Feb 27 14:00:22 sunset kernel: WARNING: Failed to create sd for 1599330
>>Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 
>>(fs/reiser4/plugin/node/node40.c:767)[nikita-494]:
>>Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95
>>Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 
>>(fs/reiser4/plugin/node/node40.c:767)[nikita-494]:
>>Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95
>>Feb 27 14:00:24 sunset kernel: reiser4[cupsd(3296)]: parse_node40 
>>(fs/reiser4/plugin/node/node40.c:767)[nikita-494]:
>>Feb 27 14:00:24 sunset kernel: WARNING: Wrong level found in node: 1 != 95
>>    
>>
> 
>Thanks,
>  
>


  reply	other threads:[~2005-03-04 14:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 19:34 reiser4 bug Szabolcs Illes
2005-02-28 14:45 ` Alex Zarochentsev
2005-03-01 12:31   ` Szabolcs Illes
2005-03-04 13:48 ` Alex Zarochentsev
2005-03-04 14:38   ` Szabolcs Illes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-11  8:58 Matt Eaton
2006-04-11  5:28 Matt Eaton
2006-04-11  5:54 ` Alexander Zarochentsev
2006-04-11  8:27   ` Michael Weissenbacher
2006-04-11  8:54   ` Avuton Olrich
2006-04-11 12:22     ` Alexander Zarochentsev
2006-04-11  6:35 ` Jake Maciejewski
2006-03-28 16:16 Reiser4 bug Alexander Gran
2006-03-28 16:37 ` Alexander Gran
2005-11-30 10:40 reiser4 bug Thomas Kuther
2004-09-05 14:25 Scheduler experiences Markus   Törnqvist
2004-09-05 15:55 ` Scheduler experiences (with Reiser4 bug report) mjt
2004-09-05 16:07   ` Reiser4 bug mjt
2004-09-05 16:07     ` Markus   Törnqvist

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=422872E8.4020301@cpc.wmin.ac.uk \
    --to=illes@cpc.wmin.ac.uk \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@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.