Steve, I can confirm that in my setup. Test is easy, as described by Scott.
I've copied over the first iso I found on my PC to my fileserver running an ext4 /data partition. Then I had some fun with md5sum: k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso 138468d380b84e6b9e9a8648efb97143 en_win_xp_pro_n.iso k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso d6b2bc09fc4df1876005f20b62364f6e en_win_xp_pro_n.iso k...@woodstock:/data/iso$ sync k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso 91cf62eee1e159774c8acee03cf88f39 en_win_xp_pro_n.iso k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso d11a45c61466f2b22757e0e449e2fe90 en_win_xp_pro_n.iso k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso f8e682be3590d48e0c266d15a804e3af en_win_xp_pro_n.iso k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso d11a45c61466f2b22757e0e449e2fe90 en_win_xp_pro_n.iso k...@woodstock:/data/iso$ md5sum en_win_xp_pro_n.iso d11a45c61466f2b22757e0e449e2fe90 en_win_xp_pro_n.iso Note that it seems to stabilized on d11a45c61466f2b22757e0e449e2fe90 after bouncing off from there once. Also note that calling sync seems to have no effect on the bug. That's certainly a fun one. -- corruption of large files reported with linux 2.6.31-14.46 on ext4 https://bugs.launchpad.net/bugs/453579 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
