reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Berny <berny@dwami.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: File copy problems kde 4.5 to 4.6.1 with reiser4
Date: Wed, 09 Mar 2011 12:38:47 +0000	[thread overview]
Message-ID: <4D7774D7.3030908@dwami.com> (raw)
In-Reply-To: <AANLkTikRbBP=XeNtvMkN=jYDVcuTZdqAM5bM=5NeAn=q@mail.gmail.com>

On 03/09/2011 10:32 AM, Serkan Kaba wrote:
> 2011/3/9 berny®<berny@dwami.com>:
>> Hi Edward,
>> first thank you for your work.
>>
>> I'm using reiser4 for all my partitions on my working machine with kernel 2.6.37 with no problems
>> except one annoying one that is going on from months.
>> When I copy a file (whatever) from one directory to another with konqueror, dolphin or krusader with
>> kde 4.6.1 the file get copied, it's size is correct but it is empty.
>>
>> This happen only in the partitions formatted with reiser4 and not on the xfs, reiser3 ones.
>>
>>
>> Thank you,
>> warm regards,
>> Paolo
>> --
>> 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
>>
>
> I suspect that it's similar to what I experienced with gnome upgrade
> back in time. My problem was due to issues in splice code path which
> GNOME switch to for file copying along the way. I already reported
> this to GNOME [1] as well as this ML [2,3]. The issue appearing in
> only uncompressed partitions is interesting, Edward already asked me
> if mine was, which isn't. My current workaround is to use a patched
> version of glib (part of gnome libs) that avoids using splice for
> reiser4 targets. If you have a KDE bugzilla account, can you also
> provide them links for discussions in the list as well as the GNOME
> bug?
>
> 1: https://bugzilla.gnome.org/show_bug.cgi?id=615346
> 2: http://marc.info/?l=reiserfs-devel&m=127096098705179&w=2
> 3: http://marc.info/?l=reiserfs-devel&m=129275181431455&w=2
> --

So it seems that also kde probably use this library to splice data from 
a pipe, I saw that it seemed resolved in 2.6.36 but it is here again in 
2.6.37.
I read your links, very good information.
I never know that kde was using this splice for copying things.
Sorry but I'm not member of kde bugzilla, I was simply searching for 
information.
The problem is that only reiser4 exhibit this problem on my system so I 
guessed that was a problem of this file system, this is the reason 
because I didn't fill a bug on the other bugzilla.

Thanks,
Paolo


> 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:[~2011-03-09 12:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09  9:18 File copy problems kde 4.5 to 4.6.1 with reiser4 berny®
2011-03-09 10:32 ` Serkan Kaba
2011-03-09 12:38   ` Berny [this message]
2011-03-09 16:40     ` Serkan Kaba
2011-03-09 16:55       ` Berny
2011-03-09 16:59         ` Serkan Kaba
2011-03-15 17:35     ` Edward Shishkin
2011-04-04 10:42       ` File copy problems kde 4.5 to 4.6.1 with reiser4 2.6.38 berny®
2011-04-05 19:36         ` Giuseppe Argentieri
2011-04-05 22:32           ` Edward Shishkin
2011-04-06  4:35             ` Serkan Kaba
     [not found]               ` <BANLkTimNoqZwW=N=5jcMm_C8cTw9ity55g@mail.gmail.com>
2011-04-06 20:07                 ` Serkan Kaba
2011-04-06 21:22                   ` Giuseppe Argentieri
2011-04-26 12:39                     ` Edward Shishkin
2011-03-09 11:46 ` File copy problems kde 4.5 to 4.6.1 with reiser4 Edward Shishkin
2011-03-09 12:46   ` Berny
  -- strict thread matches above, loose matches on Subject: below --
2011-03-16 10:19 berny®

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=4D7774D7.3030908@dwami.com \
    --to=berny@dwami.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).