From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Alexander Zarochentcev <zam@namesys.com>
Cc: thunder7@xs4all.nl, linux-kernel@vger.kernel.org
Subject: Re: reiserfs_delete_solid_item [ xxx xxx 0(1) DIR ] not found when FS full?
Date: Sun, 09 Dec 2001 15:39:59 +0300 [thread overview]
Message-ID: <3C135B9F.29A15701@namesys.com> (raw)
In-Reply-To: <20011208062921.GA3002@alpha.of.nowhere> <15378.8955.835551.333970@backtop.namesys.com>
Hi
Alexander Zarochentcev wrote:
> Jurriaan on Alpha writes:
>
> > I was copying some tree and didn't notice my file-system filling up, but
> > I did notice this on the console (and in the logs):
> >
> > Dec 8 07:17:31 alpha sudo: jurriaan : TTY=tty3 ; PWD=/var/spool ; USER=root
> > ; COMMAND=/bin/cp -ax news testnews Dec 8 07:22:03 alpha kernel: vs-5355:
> > reiserfs_delete_solid_item: [434934 434961 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_soli d_item: [434933 434961 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_solid_item: [434961 434962 0(1) DIR] not found<4>vs-5355:
> > reise rfs_delete_solid_item: [434962 434963 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_solid_item: [434962 434963 0(1) DIR] not found<4 >vs-5355:
> > reiserfs_delete_solid_item: [434962 434963 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_solid_item: [434962 434963 0(1) D IR] not found<4>vs-5355:
> > reiserfs_delete_solid_item: [434962 434963 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_solid_item: [43496 2 434963 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_solid_item: [434962 434963 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_sol id_item: [434962 434963 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_solid_item: [434962 434963 0(1) DIR] not found<4>vs-5355:
> > reis erfs_delete_solid_item: [434962 434963 0(1) DIR] not found<4>vs-5355:
> > reiserfs_delete_solid_it
> >
> > Somehow, 'delete' is not what I expect when copying. Is this something
> > to worry about?
>
> `Delete' is possible when copying. reiserfs_new_inode() fails due to no free
> space and iput() is called on partially created inode. Some items could be
> missing and delete_inode() => delete_solid_item() warns during attempt to
> delete them.
>
This warning is 100% harmless when it appears as result of mkdir which fails due to
lack of disk space.
Thanks,
vs
prev parent reply other threads:[~2001-12-09 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 6:29 reiserfs_delete_solid_item [ xxx xxx 0(1) DIR ] not found when FS full? Jurriaan on Alpha
2001-12-08 14:26 ` Alexander Zarochentcev
2001-12-09 12:39 ` Vladimir V. Saveliev [this message]
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=3C135B9F.29A15701@namesys.com \
--to=vs@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox