mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bret Towe <magnade@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs issue with 2.6.32.8
Date: Sun, 14 Feb 2010 22:46:33 -0800	[thread overview]
Message-ID: <dda83e781002142246i61737ae2j4fe7efb660b53d07@mail.gmail.com> (raw)
In-Reply-To: <dda83e781002142245l5c95d08bu214a796be289eb22@mail.gmail.com>

On Sun, Feb 14, 2010 at 10:45 PM, Bret Towe <magnade@gmail.com> wrote:
> On Sun, Feb 14, 2010 at 10:39 PM, Christian Kujau <lists@nerdbynature.de> wrote:
>> On Sun, 14 Feb 2010 at 10:23, Bret Towe wrote:
>>> I recently attempted upgrading from 2.6.31.6 to 2.6.32.8 on a local server
>>> that runs several filesystems and when trying to move or copy or create a file
>>> on a reiserfs system that was sitting on lvm over raid5(not sure if
>>> that matters)
>>> I would get mv or cp to return Invalid Argument and not doing anything
>>> moving files from xfs to xfs worked fine tho
>>
>> I'm running 2.6.32 (and now 2.6.33) with reiserfs filesystems too and
>> cannot reproduce what you're seeing. Can you run mv/cp through strace and
>> provide the output? Also, if you can: maybe setting REISERFS_CHECK in your
>> kernel config might reveal something useful.
>>
>> Is this reproducible with 2.6.33-rcX as well? If so, I'd recommend to try
>> again with plain 2.6.32 and if it's still there, I see no other way to
>> narrow it down but with a git bisection (man git-bisect).
>
> I forgot to note that file operations on the reiserfs partitions
> worked fine inside themselves
>
> I guess I will see about running a few other kernels then over next
> few days as time permits
> first I will try is the reiserfs_check option tho then revert to .32
> and go from there
>

and I will also forget to hit reply all in the time being

  parent reply	other threads:[~2010-02-15  6:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 18:23 Bret Towe
2010-02-14 23:27 ` Rafael J. Wysocki
2010-02-15  6:39 ` Christian Kujau
     [not found]   ` <dda83e781002142245l5c95d08bu214a796be289eb22@mail.gmail.com>
2010-02-15  6:46     ` Bret Towe [this message]
2010-08-30 10:49       ` UIO and Fedora 13 (kernel 33.6) Armin Steinhoff
2010-08-30 16:24         ` Hans J. Koch
2010-08-31  6:57           ` Armin Steinhoff
2010-08-31 10:35             ` Hans J. Koch
2010-08-31 13:23               ` Armin Steinhoff
2010-09-01  7:31               ` Armin Steinhoff
2010-09-01 18:56                 ` Hans J. Koch
2010-09-01 21:40                   ` Armin Steinhoff
2010-09-01 22:14                     ` Hans J. Koch
2010-08-30 11:07       ` UIO and Fedora 13 (kernel 33.6) / kernel module corrected Armin Steinhoff
2010-02-24  5:31   ` reiserfs issue with 2.6.32.8 Bret Towe
2010-02-24  7:03     ` Christian Kujau
2010-02-25  2:17       ` Bret Towe
2010-03-04  3:00       ` Bret Towe
2010-03-04 21:37         ` Christian Kujau
2010-03-04 22:53           ` Bret Towe
2010-03-05  7:36             ` Christian Kujau

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=dda83e781002142246i61737ae2j4fe7efb660b53d07@mail.gmail.com \
    --to=magnade@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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

all inboxes | Powered by JetHome®