In <97cbd1a90907291319wc4cca42r87cb799f94fe8...@mail.gmail.com>, Josh Kelley
wrote:
>I'm not sure the
>best way to further track down the problem from here. Is there an
>easy way (short of compiling my own kernel) to try out 2.6.27?
Compiling your own kernel from upstream sources is not *that*
On Wed, Jul 29, 2009 at 9:54 AM, Emil Pedersen wrote:
> Don't know if it is at all related, but I had some usb sticks
> behaving quiet strange too (on a debian etch 64bit).
>
> The symptons where that a file (kernel actually) that was copied
> to the stick could not be run the next time the stick w
--On onsdag, juli 29, 2009 09.07.16 -0400 Josh Kelley
wrote:
On Wed, Jul 29, 2009 at 12:31 AM, Owen
Townend wrote:
Just to be clear here: When using one of these fraudulent drives
filling it up will produce no errors. Reading it back will show
corruption once passed the actual size of the
On Wed, Jul 29, 2009 at 12:31 AM, Owen Townend wrote:
> Just to be clear here: When using one of these fraudulent drives
> filling it up will produce no errors. Reading it back will show
> corruption once passed the actual size of the device.
>
> Your comment didn't mention whether you were able to
2009/7/29 Josh Kelley :
> On Tue, Jul 28, 2009 at 10:33 AM, Sven Joachim wrote:
[snip]
>> There had been cases of USB memory sticks with manipulated controllers
>> produced by fraudulent manufacturers. These sticks reported a higher
>> capacity than they really had. They never reported read or wr
On Tue, Jul 28, 2009 at 10:33 AM, Sven Joachim wrote:
> On 2009-07-28 15:42 +0200, Josh Kelley wrote:
>> Turning off has_journal or adding -o data=journal fixes the
>> immediately preceding problem. (I haven't tested it for our cloning
>> procedure.) However, I don't want to go back to ext2, and
On 2009-07-28 15:42 +0200, Josh Kelley wrote:
> We use Debian for some embedded devices that use off-the-shelf flash
> drives for their primary storage. Since upgrading from etch to lenny
> and tweaking our partition layout, we've started seeing filesystem
> corruption occur very rapidly after we
We use Debian for some embedded devices that use off-the-shelf flash
drives for their primary storage. Since upgrading from etch to lenny
and tweaking our partition layout, we've started seeing filesystem
corruption occur very rapidly after we clone the filesystem (via
partimage and resize2fs). W
8 matches
Mail list logo
