From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753741Ab0CDDA2 (ORCPT ); Wed, 3 Mar 2010 22:00:28 -0500 Received: from mail-qy0-f172.google.com ([209.85.221.172]:56312 "EHLO mail-qy0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753267Ab0CDDAZ convert rfc822-to-8bit (ORCPT ); Wed, 3 Mar 2010 22:00:25 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=U3H4eq+O0CLAIFSos8wZCLtHKUhrCzzLI/AEkdlrCJ90RZclzggpPaUo5d7Nc5oISa /sqDFXRl2Gc0akh8JzLKOWD63ZxtGBGcyFPsZvWSbkHh2RjM5WqXc92TzdVfJGvQGPrQ pbqiJ3e16rK/wHFtlplSNAkW0TQVvcQ9E5E9c= MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 3 Mar 2010 19:00:24 -0800 Message-ID: Subject: Re: reiserfs issue with 2.6.32.8 From: Bret Towe To: Christian Kujau Cc: Linux Kernel Mailing List , reiserfs-devel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 23, 2010 at 11:03 PM, Christian Kujau wrote: > On Tue, 23 Feb 2010 at 21:31, Bret Towe wrote: >> ok attached is strace log of cp on 2.6.32.9 > > I've run cp through strace as well (copying something from an XFS > partition to a reiserfs partition, I guess that's what you did too), and > noticed a small difference at the end: > > < open("/home/foo/1", O_RDONLY)          = 3 > < fstat(3, {st_mode=S_IFREG|0640, st_size=755, ...}) = 0 > < open("2", O_WRONLY|O_CREAT|O_EXCL, 0640) = 4 > > While your cp(1) did: > >> open("downloads/[DB]_Bleach_258_[27104F7A].avi", O_RDONLY) = 3 >> fstat(3, {st_mode=S_IFREG|0644, st_size=178308328, ...}) = 0 >> open("/mdhd/media/Episodes/unwatched/[DB]_Bleach_258_[27104F7A].avi", O_WRONLY|O_CREAT|O_EXCL, 0644) = -1 EINVAL (Invalid argument) > > > And open(2) will return -EINVAL when: >   - The implementation does not support synchronised I/O for this file. >   - The value of the oflag argument is not valid. > > As we're not passing O_SYNC, it's the latter, if I read this correctly. Which > still doesn't explain *why* (the filesystem?) returns "invalid flag". > >> now I've had a hd drop out of raid (running checks on it atm) > > Hm, maybe it's all hardware related after all, let's see what these checks > turn up. Strange though, that nothing gets reported in dmesg... well the hardware update ended up changing more than I thought it would now on 32bit from 64bit so config is completely new also for the kernel end result tho is I'm on a 2.6.33 kernel and no issues