All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Chris Gentile <cnjgentile@gmail.com>
Cc: Mathieu Belanger <m@thieu.so>,
	reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: Issue in my API re-implementation in my kernel 3.11
Date: Mon, 23 Sep 2013 13:17:48 +0200	[thread overview]
Message-ID: <5240235C.9090903@gmail.com> (raw)
In-Reply-To: <52401F7C.2040309@gmail.com>

23.09.2013 13:01, Chris Gentile пишет:
> Mathieu et, all ,
>
> Fixes seemed to have fixed the corruption issue thus far. Re-emerging
> 1000+ packages on Gentoo (tons of small reads/writes on SSD) with no
> problems yet. Also, just downloaded the Linux-next patch from this
> morning
> (https://www.kernel.org/pub/linux/kernel/next/patch-v3.12-rc1-next-20130923.xz)
> and applied on top of your Reiser4-for-3.12-rc1 branch recompiled
> re-installed NVidia (thanks for fixing that btw!) and resuming compiling
> as we speak. Going strong still and fast.
>
> Not sure if it makes much difference but I use no compression just
> mkfs.reiser4 -o formatting=smart on SSD drives.


Which version of mkfs (mkfs.reiser4 --version)?
In 1.0.8 compression is enabled by default.


>
> Are there any special options I should be using on SSD arrays?
>
> Addressing the compression angle, does formatting an array with one of
> the compression options (lzo perhaps?) have significant overhead?


What overhead do you mean?


> Storage space is not a concern however if there is very little overhead
> I'd like to backup my data and do some benchmarking.  Please advise at
> your convenience.
>
>
> Thanks again,
> Chris
>
> On 09/21/13 19:53, Christopher Gentile wrote:
>> I've experienced corruption in the 3.12-rc1 on the git tree and just
>> did a fsck.reiser4 --build-fs. Also re-downloaded the tree and
>> recompiled as it looks like you've made changes I'll keep you posted.
>>
>>
>>
>> On Sat, Sep 21, 2013 at 3:18 AM, Mathieu Belanger <m@thieu.so> wrote:
>>> In my kernel 3.11 on my git, I have re-implemented an API because I did not
>>> know how to port the reiser4 to the new API (readdir -> iterate).
>>>
>>> I did not get any problem with reiser4 or reiserfs -but- after installing
>>> the 3.12-rc1 kernel and rebooting, the kernel was missing and the grub.conf
>>> was total garbage. The /boot is EXT2 on my system.
>>>
>>> readdir is for reading dir mostly, I don't know if it's the cause of the
>>> corruption or if it did not sync properly but still, if you want to play
>>> with a ext2 partition and you use the kernel 3.11 from my git, reboot to
>>> another kernel before, just as precaution.
>>>
>>> The kernel 3.12-rc1 is not affected if it's because of that readdir API
>>> reimplementation because it's based on the Ivan port + shrinker new API
>>> patchs for reiser4.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2013-09-23 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21  3:18 Issue in my API re-implementation in my kernel 3.11 Mathieu Belanger
2013-09-21 19:53 ` Christopher Gentile
2013-09-23 11:01   ` Chris Gentile
2013-09-23 11:17     ` Edward Shishkin [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=5240235C.9090903@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=cnjgentile@gmail.com \
    --cc=m@thieu.so \
    --cc=reiserfs-devel@vger.kernel.org \
    /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.