these calls seems to
help
measureExactStorage(imcs);
break;
}
On Fri, Mar 21, 2014 at 12:09 AM, Nilesh More wrote:
> I now know the source of p
these calls seems to
help
measureExactStorage(imcs);
break;
}
On Fri, Mar 21, 2014 at 12:09 AM, Nilesh More nilesh99...@gmail.com wrote:
I now know
,
Nilesh
On Thu, Mar 20, 2014 at 12:38 AM, Nilesh More wrote:
> Hi Ted,
>
>>And I'll repeat the comments I made a few weeks ago. Last time you
>>reported this, you included a dmesg output which included this:
>
>> [ 413.607849] usb 2-1.1: USB disconnect, device number
,
Nilesh
On Thu, Mar 20, 2014 at 12:38 AM, Nilesh More nilesh99...@gmail.com wrote:
Hi Ted,
And I'll repeat the comments I made a few weeks ago. Last time you
reported this, you included a dmesg output which included this:
[ 413.607849] usb 2-1.1: USB disconnect, device number 12
[ 414.022630
plug the USB drive. It
might require couple of hotplug/hotunplug to see this issue.
Thank you,
Nilesh
On Thu, Mar 20, 2014 at 12:31 AM, wrote:
> On Thu, Mar 20, 2014 at 12:05:44AM +0530, Nilesh More wrote:
>> Hi all,
>>
>> First of all sorry for the lengthy mail but I did
Hi all,
First of all sorry for the lengthy mail but I did not want to miss out
on any details.
The following issue that I am reporting occurs when I plugin the USB
drive on android tablet with USB mount support. Please note that this
issue may or may not occur the first time I hotplug the USB
Hi all,
First of all sorry for the lengthy mail but I did not want to miss out
on any details.
The following issue that I am reporting occurs when I plugin the USB
drive on android tablet with USB mount support. Please note that this
issue may or may not occur the first time I hotplug the USB
. It
might require couple of hotplug/hotunplug to see this issue.
Thank you,
Nilesh
On Thu, Mar 20, 2014 at 12:31 AM, ty...@mit.edu wrote:
On Thu, Mar 20, 2014 at 12:05:44AM +0530, Nilesh More wrote:
Hi all,
First of all sorry for the lengthy mail but I did not want to miss out
on any details
while
invalidating them, incorrect data gets written to fat disk
inodes(directory inodes) which results in the "invalid access to FAT"
error prints.
I guess next step would be to try and understand the page allocations
in efi_partition and msdos_partition calls.
Thank you,
Nilesh
On Sat, M
wrote:
> On Fri, Mar 07, 2014 at 01:39:45AM +0530, Nilesh More wrote:
>> Hi all,
>>
>> I am working on android bug wherein directory entries of ext4 file
>> system get corrupted when USB is hotplugged (with auto mount support
>> enabled).
>>
>> The l
ty...@mit.edu wrote:
On Fri, Mar 07, 2014 at 01:39:45AM +0530, Nilesh More wrote:
Hi all,
I am working on android bug wherein directory entries of ext4 file
system get corrupted when USB is hotplugged (with auto mount support
enabled).
The logs as below:
[ 413.607849] usb 2-1.1: USB
data gets written to fat disk
inodes(directory inodes) which results in the invalid access to FAT
error prints.
I guess next step would be to try and understand the page allocations
in efi_partition and msdos_partition calls.
Thank you,
Nilesh
On Sat, Mar 8, 2014 at 1:48 AM, Nilesh More nilesh99
going to debug further to try and get to root cause. Before that
wanted to ask if is this A KNOWN ISSUE ? If not, any suggestions
that would help me to quickly root cause this ?
Thank you for your help,
Nilesh
On Fri, Mar 7, 2014 at 1:35 AM, Nilesh More wrote:
> Hi all,
>
> I am workin
this ?
Thank you for your help,
Nilesh
On Fri, Mar 7, 2014 at 1:35 AM, Nilesh More nilesh99...@gmail.com wrote:
Hi all,
I am working on android bug wherein directory entries of ext4 file system
get corrupted when USB is hotplugged (with auto mount support enabled).
The logs as below:
[ 413.607849
14 matches
Mail list logo
