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:46:36 +0000 [thread overview]
Message-ID: <4D7776AC.2050906@dwami.com> (raw)
In-Reply-To: <4D7768A7.10107@gmail.com>
Hi Edward, thanks for answering.
No sync doesn't make any difference, I need to unmount.
I don't get any errors, for example if I copy a txt file and I open it
with kwrite, it is simply empty but I get no error from application or
os (like dmesg and alike) and ls or konqueror show me the correct size
of the file, it is simply apparently empty.
If I do file <name> I got empty file.
Thanks,
Paolo
On 03/09/2011 11:46 AM, Edward Shishkin wrote:
> On 03/09/2011 10:18 AM, berny® wrote:
>> Hi Edward,
>
> Hello.
>
>> 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.
>>
>> If I restart the pc, when I'm back all the files that were empty are
>> now ok, it is like on un
>> mounting the files get finalized and then on the next boot they are
>> normally accessible.
>
>
> Does sync(1) without umount make them accessible?
>
>
>> No errors are shown during copy and file system is clean.
>
> Are there any suspicious kernel messages when trying
> to access the "empty" files?
>
> Thanks,
> Edward.
>
>
>> I discovered that this is also signaled like a kde bug 251392 with
>> status unconfirmed.
>>
>> If I copy from a terminal with cp, rsync, mc the file get copied
>> correctly so it is only in the
>> combination kde + reiser4 that I get problems.
>> Don't know if it is a bug of reiser4 or of kde.
>>
>> My mount options are no_write_barrier,dont_load_bitmap, the rest is
>> default, the volumes are normal,
>> I mean not cryptocompress.
>> An interesting thing, if I format the reiser4 with cryptocompress
>> support (-o create=ccreg40,
>> compress=lzo1) this behavior don't happen, I mean the files are copied
>> correctly so it seems only to
>> affect normal uncompressed reiser4 volumes.
>> Hope this can be of help to you.
>>
>> 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
>
> --
> 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
next prev parent reply other threads:[~2011-03-09 12:46 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
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 [this message]
-- 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=4D7776AC.2050906@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 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.