Re: Back to BFS+TOI issue

Yep, i can reproduce it reliably.

In case of LZO TOI fails with:

===
[    2.868511] Stopping fuse filesystems.
[    2.868517] Freezing user space processes ... (elapsed 0.01 seconds)
done.
[    3.009621] usb 7-1: New USB device found, idVendor=046d, idProduct=c51b
[    3.009627] usb 7-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[    3.009631] usb 7-1: Product: USB Receiver
[    3.009634] usb 7-1: Manufacturer: Logitech
[    3.105586] ...20%
[    3.231212]
[    3.231214] Breaking out of I/O loop because of result code -22.
[    5.514041]
[    5.514042] Breaking out of I/O loop because of result code -22.
[    5.514046]
[    5.515013] Waited for i/o due to readahead not ready 60 times.
[    5.515016] Waited for i/o due to synchronous I/O 3 times.
[    5.515878] Restarting all filesystems ...
[    5.515882] Restarting tasks ... done.
===

In case of LZF TOI fails with:

===
[    3.479015] Stopping fuse filesystems.
[    3.479022] Freezing user space processes ... (elapsed 0.01 seconds)
done.
[    3.603296] usb 7-1: New USB device found, idVendor=046d, idProduct=c51b
[    3.603302] usb 7-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[    3.603306] usb 7-1: Product: USB Receiver
[    3.603309] usb 7-1: Manufacturer: Logitech
[    3.975868] ...20%
[    4.941101] Decompression yielded 3544 bytes instead of 4096.
[    4.941105]
[    4.941106] Breaking out of I/O loop because of result code -5.
[    6.014157] Decompression yielded 4067 bytes instead of 4096.
[    6.014161]
[    6.014162] Breaking out of I/O loop because of result code -5.
[    6.014166]
[    6.014192] Waited for i/o due to readahead not ready 3367 times.
[    6.014195] Waited for i/o due to synchronous I/O 3 times.
[    6.014197] Waited for i/o due to throughput_throttle 35 times.
[    6.015078] Restarting all filesystems ...
[    6.015082] Restarting tasks ... done.
===

What parameters I have to pass to kernel to check single-threaded job?

12.03.12 12:47, Nigel Cunningham написав(ла):
> Hi.
> 
> On 12/03/12 20:51, Oleksandr Natalenko wrote:
>> The second interesting thing we've discovered recently is: if
>> hibernation has done with CFS, thawing with BFS is OK. The issue is not
>> about decompression, *it's about compression*.
> Sorry for my slowness - fwiw, I started today to write the script to do
> automatic posting to the website of patches from the git trees, so
> TuxOnIce isn't dead yet :)
> 
> Anyway...
> 
> Can you reliably reproduce the issue? If so, could you see if changing
> the compression algorithm or running single threaded makes any difference?
> 
> Regards,
> 
> Nigel

_______________________________________________
TuxOnIce-devel mailing list
[email protected]
http://lists.tuxonice.net/listinfo/tuxonice-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPXh1kAAoJELftKrVLdx04H78H/0vKJ26YVAvHj8c1ANuIQjI1
A/B6mZbEWfghLVyUq1seVEpZI71w3L96TkdyEqT7iShfutrTwBt4aoeXlfqDuZRo
VIyYyJhcXC3/3tqjfyrncHPbOn/eUwg6oB0IY0vhnhb4SwlzwV9TDUzr498ZwRzY
iXoxMe6JrgCDXRCZkgYfFZNJPjiA/7tZHab7YnlyVeld0y3Ih8iv18/FRqrYPXMn
nNmrrqOzZgz4lGG0VBXtql+/yDRKSvfh1gwnvNSDSxCiqlhQkcPj5dOT82E1dqMq
RhGBq4swWhu1JnUsnF8qp3lOMQsixFrVLPglWpnYcaDQ8SZ7DuJTC5CDjIXXvjY=
=lIj4
-----END PGP SIGNATURE-----