All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Fertman <vitaly@namesys.com>
To: Francesco Biscani <frbiscani@jumpy.it>, reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 wrong size error (?)
Date: Fri, 13 Aug 2004 00:31:13 +0400	[thread overview]
Message-ID: <200408130031.13061.vitaly@namesys.com> (raw)
In-Reply-To: <200408122138.46787.frbiscani@jumpy.it>

On Thursday 12 August 2004 23:38, Francesco Biscani wrote:
> On Tuesday 10 August 2004 20:09, Francesco Biscani wrote:
> > Hi,
> >
> > > are messages about 'wrong size' or about 'wrong bytes' or both?
> >
> > I'm _almost_ sure it's about "wrong bytes". I'll confirm ASAP. Are they
> > potentially harmful?
> >
> > Oh, BTW, "debugfs -C" worked ok here.
> >
> > Regards,
> >
> >   Francesco
>
> An update for those interested:
>
> - it was a "wrong bytes" message. All the bytes of affected objects were
> doubled. Corrected with --fix and using now auto-snapshot for
> 2.6.8-rc4-mm1. Let's see if it happens again.

this was fixed recently.

> - debugfs -C worked ok also on my / partition.
>
> BTW, debugfs -p showed also that the default plugin for fibration was
> changed, from dot-o to ext-1. But if I create a dir it is still
> dot-o-fibrated. Am I missing something here? Should I mount with some
> special options to have ext-1 fibration as default?

default plugins in progs play role for mkfs only, and they have nothing to
do with already created fs. You have created it with dot-o default, so the 
current fibration fs default is dot-o, and you can change it for some partitcular 
directory only, an empty one, with :
	echo -e "ext-1\0" > dir/metas/plugin/fibration
Then all children will be created with with ext-1 also.

-- 
Thanks,
Vitaly Fertman


  parent reply	other threads:[~2004-08-12 20:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 17:25 Apache2 problems Tom Lanyon
2004-08-09 17:29 ` mjt
2004-08-09 17:50   ` Hans Reiser
2004-08-09 17:59     ` Tom Lanyon
2004-08-09 19:59 ` Alex Zarochentsev
2004-08-10 11:31 ` Alex Zarochentsev
2004-08-10 17:48 ` fsck.reiser4 wrong size error (?) Francesco Biscani
2004-08-10 17:56   ` Vitaly Fertman
2004-08-10 18:09     ` Francesco Biscani
2004-08-10 18:30       ` Vitaly Fertman
2004-08-10 18:37       ` Vladimir V. Saveliev
2004-08-12 19:38       ` Francesco Biscani
2004-08-12 20:08         ` Alex Zarochentsev
2004-08-12 20:31         ` Vitaly Fertman [this message]
2004-08-12 21:08           ` Francesco Biscani
2004-08-13  9:16             ` Alex Zarochentsev
2004-08-13  9:31               ` mjt
2004-08-13  9:43                 ` Vladimir V. Saveliev
2004-08-13  9:44                   ` mjt
2004-08-13  9:50                     ` Vladimir V. Saveliev
2004-08-13 10:00                     ` Nikita Danilov
2004-08-13 10:01                       ` mjt
2004-08-13 10:46                         ` Vladimir V. Saveliev
2004-08-13 11:10                           ` mjt
2004-08-13 20:06               ` Francesco Biscani
2004-08-13 20:26                 ` Matt Stegman
2004-08-13 20:45                   ` Francesco Biscani
2004-08-13 20:54                     ` Matt Stegman
2004-08-14  8:46                   ` 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=200408130031.13061.vitaly@namesys.com \
    --to=vitaly@namesys.com \
    --cc=frbiscani@jumpy.it \
    --cc=reiserfs-list@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.