FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 07-07-2011, 05:13 PM
Michał Piotrowski
 
Default glibc 2.14-4 eats my data ( F15 ext3, eCryptfs + samba = data corruption ( F15 "Error mounting eCryptfs: Input/output error" on different disks))

Hi,

When I did a glibc downgrade to 2.13.90-9 eCryptfs mount problem no
longer appears, also there is no data corruption problem. Glibc
changes somehow breaks eCryptfs and probably also samba.

W dniu 5 lipca 2011 21:25 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:
> W dniu 5 lipca 2011 21:13 użytkownik nodata <lsof@nodata.co.uk> napisał:
>> On 05/07/11 21:11, Michał Piotrowski wrote:
>>> Hi,
>>>
>>> W dniu 16 czerwca 2011 21:37 użytkownik Michał Piotrowski
>>> <mkkp4x4@gmail.com> *napisał:
>>>> Hi,
>>>>
>>>> Do anyone noticed any problems with mounting eCryptfs recently on F15?
>>>> It seems to me unlikely that I have an I/O errors on few disks.
>>>> Especially if only eCryptfs reports them.
>>>>
>>>
>>> I've got two dirs
>>>
>>> /home/s1 - ext3
>>> /home/s2 - ext3 + eCryptfs
>>>
>>> If I copy a file from my laptop to /home/s1 it has md5 sum
>>> c7da3acc8e85f64661b49b9788771bf6
>>> when I copy this file from shell to /home/s2 it has the same md5 sum
>>> c7da3acc8e85f64661b49b9788771bf6
>>>
>>> If I copy the same file from my laptop to /home/s2 I get a strange error
>>> in Total commander "please remove the write protection" - TC's progress bar
>>> doesn't show any progress - after copying file has correct size, but
>>> it's totally
>>> broken - md5 sum
>>> f26767c3aed2f6e639ddb9ad6601daaf
>>>
>>> Does anyone have any idea what could be wrong? I guess that data corruption
>>> problem is related to this strange "Error mounting eCryptfs: [-5]
>>> Input/output error"
>>> message.
>>>
>>>
>>
>> Check dmesg,
>
> nothing here
>
>> your the logs
>
> Some samba problem
>
> Jul *5 21:21:21 ozzy smbd[6939]: [2011/07/05 21:21:21.750117, *0]
> lib/util_sock.c:1514(matchname)
> Jul *5 21:21:21 ozzy smbd[6939]: * matchname: host name/address
> mismatch: ::ffff:192.168.101.100 != dio
> Jul *5 21:21:21 ozzy smbd[6939]: [2011/07/05 21:21:21.751328, *0]
> lib/util_sock.c:1635(get_peer_name)
> Jul *5 21:21:21 ozzy smbd[6939]: * Matchname failed on dio
> ::ffff:192.168.101.100
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.603368, *0]
> lib/util_sock.c:680(write_data)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.604101, *0]
> lib/util_sock.c:1441(get_peer_addr_internal)
> Jul *5 21:21:30 ozzy smbd[4815]: * getpeername failed. Error was Drugi
> koniec nie jest połączony
> Jul *5 21:21:30 ozzy smbd[4815]: * write_data: write failure in
> writing to client 0.0.0.0. Error Przerwany potok
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.607351, *0]
> smbd/process.c:79(srv_send_smb)
> Jul *5 21:21:30 ozzy smbd[4815]: * Error writing 62 bytes to client.
> -1. (Drugi koniec nie jest połączony)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.608346, *0]
> lib/util_sock.c:680(write_data)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.608883, *0]
> lib/util_sock.c:1441(get_peer_addr_internal)
> Jul *5 21:21:30 ozzy smbd[4815]: * getpeername failed. Error was Drugi
> koniec nie jest połączony
> Jul *5 21:21:30 ozzy smbd[4815]: * write_data: write failure in
> writing to client 0.0.0.0. Error Przerwany potok
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.610048, *0]
> smbd/process.c:79(srv_send_smb)
> Jul *5 21:21:30 ozzy smbd[4815]: * Error writing 55 bytes to client.
> -1. (Drugi koniec nie jest połączony)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.612862, *0]
> lib/util_sock.c:680(write_data)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.613797, *0]
> lib/util_sock.c:1441(get_peer_addr_internal)
> Jul *5 21:21:30 ozzy smbd[4815]: * getpeername failed. Error was Drugi
> koniec nie jest połączony
> Jul *5 21:21:30 ozzy smbd[4815]: * write_data: write failure in
> writing to client 0.0.0.0. Error Przerwany potok
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.615032, *0]
> smbd/process.c:79(srv_send_smb)
> Jul *5 21:21:30 ozzy smbd[4815]: * Error writing 53 bytes to client.
> -1. (Drugi koniec nie jest połączony)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.616071, *0]
> lib/util_sock.c:680(write_data)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.616580, *0]
> lib/util_sock.c:1441(get_peer_addr_internal)
> Jul *5 21:21:30 ozzy smbd[4815]: * getpeername failed. Error was Drugi
> koniec nie jest połączony
> Jul *5 21:21:30 ozzy smbd[4815]: * write_data: write failure in
> writing to client 0.0.0.0. Error Przerwany potok
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.617768, *0]
> smbd/process.c:79(srv_send_smb)
> Jul *5 21:21:30 ozzy smbd[4815]: * Error writing 75 bytes to client.
> -1. (Drugi koniec nie jest połączony)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.619713, *0]
> lib/util_sock.c:680(write_data)
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.620268, *0]
> lib/util_sock.c:1441(get_peer_addr_internal)
> Jul *5 21:21:30 ozzy smbd[4815]: * getpeername failed. Error was Drugi
> koniec nie jest połączony
> Jul *5 21:21:30 ozzy smbd[4815]: * write_data: write failure in
> writing to client 0.0.0.0. Error Przerwany potok
> Jul *5 21:21:30 ozzy smbd[4815]: [2011/07/05 21:21:30.621454, *0]
> smbd/process.c:79(srv_send_smb)
> Jul *5 21:21:30 ozzy smbd[4815]: * Error writing 75 bytes to client.
> -1. (Drugi koniec nie jest połączony)
> Jul *5 21:21:33 ozzy smartd[558]: Device: /dev/sdd [SAT], is back in
> ACTIVE or IDLE mode, resuming checks (7 checks skipped)
>
>
>> and the file sizes.
>
> File size is correct
>
>> selinux perhaps?
>
> disabled
>
>
>
> What is perhaps important is that the problem appears for files > +/- 1GB.
>
>
>
> --
> Best regards,
> Michal
>
> http://eventhorizon.pl/
>



--
Best regards,
Michal

http://eventhorizon.pl/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 07-11-2011, 02:04 PM
Michał Piotrowski
 
Default glibc 2.14-4 eats my data ( F15 ext3, eCryptfs + samba = data corruption ( F15 "Error mounting eCryptfs: Input/output error" on different disks))

CC'ing devel


---------- Wiadomość przekazana dalej ----------
Od: Michał Piotrowski <mkkp4x4@gmail.com>
Data: 9 lipca 2011 10:59
Temat: Re: glibc 2.14-4 eats my data (Re: F15 ext3, eCryptfs + samba =
data corruption (Re: F15 "Error mounting eCryptfs: [-5] Input/output
error" on different disks))
Do: Michal Hlavinka <mhlavink@redhat.com>


W dniu 9 lipca 2011 10:29 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:
> Hi,
>
> W dniu 8 lipca 2011 20:08 użytkownik Michal Hlavinka
> <mhlavink@redhat.com> napisał:
>> Hi,
>>
>> please check if this package changes anything for you:
>>
>> http://kojipkgs.fedoraproject.org/scratch/mhlavink/task_3187528/
>
> unfortunately there is no difference

I'm attaching valgrind output. I checked your patch and it removes
correctly all uses of memcpy so it seems that memcpy only covered the
root of the problem.

>
>>
>> thanks
>>
>> On Friday 08 of July 2011 18:32:55 you wrote:
>>> W dniu 8 lipca 2011 18:21 użytkownik Michał Piotrowski
>>>
>>> <mkkp4x4@gmail.com> napisał:
>>> > Hi,
>>> >
>>> > 2011/7/8 Andreas Schwab <schwab@redhat.com>:
>>> >> Use valgrind.
>>> >
>>> > I attach valgrind output.
>>> >
>>> > ==1312== 1 errors in context 1 of 116:
>>> > ==1312== Source and destination overlap in memcpy(0xaef1590, 0xaef1593,
>>> > 76) ==1312== * *at 0x4C283B6: memcpy@@GLIBC_2.14
>>> > (mc_replace_strmem.c:653) ==1312== * *by 0x401835: ??? (in
>>> > /sbin/mount.ecryptfs)
>>> > ==1312== * *by 0x5E3039C: (below main) (in /lib64/libc-2.14.so)
>>>
>>> I installed ecryptfs-utils-debuginfo package and now it's more readable
>>>
>>> ==1815== 1 errors in context 1 of 116:
>>> ==1815== Source and destination overlap in memcpy(0xaef1590, 0xaef1593, 76)
>>> ==1815== * *at 0x4C283B6: memcpy@@GLIBC_2.14 (mc_replace_strmem.c:653)
>>> ==1815== * *by 0x401835: main (string3.h:52)
>>>
>>> > Could this be related to
>>> > *- Fix static linking with checking x86/x86-64 memcpy (BZ#12653)
>>> > or is it an eCryptfs problem?
>>> >
>>> >> Andreas.
>>> >>
>>> >> --
>>> >> Andreas Schwab, schwab@redhat.com
>>> >> GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 *5EC7 45C6 250E 6F00
>>> >> 984E
>>> >> "And now for something completely different."
>>> >> --
>>> >> devel mailing list
>>> >> devel@lists.fedoraproject.org
>>> >> https://admin.fedoraproject.org/mailman/listinfo/devel
>>> >
>>> > --
>>> > Best regards,
>>> > Michal
>>> >
>>> > http://eventhorizon.pl/
>>
>
>
>
> --
> Best regards,
> Michal
>
> http://eventhorizon.pl/
>
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 05:21 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org