public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: Jan De Luyck <lkml@kcore.org>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [2.4.18]: Reiserfs: vs-2120: add_save_link: insert_item	returned -28
Date: Fri, 16 Jan 2004 11:48:10 +0300	[thread overview]
Message-ID: <4007A54A.3030005@namesys.com> (raw)
In-Reply-To: <1074241063.2251.41.camel@tribesman.namesys.com>

Vladimir Saveliev wrote:

>Hello
>
>On Fri, 2004-01-09 at 18:22, Jan De Luyck wrote:
>  
>
>>Hello list,
>>
>>Today I discovered I could no longer create files on one of my boxes, which 
>>still runs 2.4.18 (box is too far away to upgrade right now). It gives me 
>>'disk full' messages.
>>
>>The following message is all over my logs since January 3:
>>
>>vs-2120: add_save_link: insert_item returned -28
>>
>>    
>>
>
>This is just a warning. You should be able to free some disk space by
>removing some files.
>
>
>
>  
>
>>I can't seem to find much on this issue, is this a bug in reiserfs (which is 
>>fixed in a later version)? Is something wrong with the fs itself?
>>
>>Thanks for answers.
>>
>>[I'm not subscribed @ reiserfs-list, so please cc me with answers from that 
>>list]
>>
>>Jan
>>    
>>
>
>
>
>  
>
why do we generate this warning?  It should be fixed, yes?

-- 
Hans



  reply	other threads:[~2004-01-16  8:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 15:22 [2.4.18]: Reiserfs: vs-2120: add_save_link: insert_item returned -28 Jan De Luyck
2004-01-09 17:00 ` Jan De Luyck
2004-01-16  8:17 ` Vladimir Saveliev
2004-01-16  8:48   ` Hans Reiser [this message]
2004-01-16 15:52     ` Oleg Drokin
2004-01-16 16:19   ` Valdis.Kletnieks
2004-01-16 16:26     ` Vladimir Saveliev

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=4007A54A.3030005@namesys.com \
    --to=reiser@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.org \
    --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