reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Łukasz Mierzwa" <prymitive@pcserwis.net>
To: "Vladimir V. Saveliev" <vs@namesys.com>,
	"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: reiser4 oops
Date: Mon, 03 Jul 2006 13:51:59 +0200	[thread overview]
Message-ID: <op.tb328xkxd4os1z@localhost> (raw)
In-Reply-To: <1151921448.6335.42.camel@tribesman.namesys.com>

Dnia Mon, 03 Jul 2006 12:10:48 +0200, Vladimir V. Saveliev  
<vs@namesys.com> napisa³:


> would you please check whether this patch helps?
> ftp://ftp.ru.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm5/broken-out/reiser4-run-truncate_inode_pages-in-reiser4_delete_inode.patch

I have deleted some old files, unmerged xine from my system and compiled  
it again and this time there was no problem, but I'm rebuilding my whole  
system so I will aplly this patch and see if I get another one oops.

thanks

  parent reply	other threads:[~2006-07-03 11:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-01 20:08 reiser4 oops Łukasz Mierzwa
2006-07-01 20:13 ` Łukasz Mierzwa
2006-07-03  4:24 ` Jake Maciejewski
     [not found]   ` <1151921448.6335.42.camel@tribesman.namesys.com>
2006-07-03 11:51     ` Łukasz Mierzwa [this message]
2006-07-03 23:23     ` Jake Maciejewski
2006-07-07  7:18       ` Jake Maciejewski
     [not found]         ` <1152278167.6236.21.camel@tribesman.namesys.com>
2006-07-11  6:43           ` Jake Maciejewski
  -- strict thread matches above, loose matches on Subject: below --
2009-07-02  8:34 Reiser4 oops Piotr Sawuk
2010-12-19 19:01 Reiser4 Oops Андрей Колченко
2010-12-19 22:33 ` Edward Shishkin
2010-12-20 22:31   ` Edward Shishkin
     [not found]     ` <AANLkTinbSRgNhi5heC2npLNzU4xsuUjzEXBD5qDBiYDw@mail.gmail.com>
2011-01-05 12:10       ` Edward Shishkin

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=op.tb328xkxd4os1z@localhost \
    --to=prymitive@pcserwis.net \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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 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).