Bug#685726: linux-image-3.2.0-3-amd64: return error when trying
The problem solved in Debian Wheezy for kernel linux-image-3.2.0-4-amd64 3.2.32-1 amd64 Linux 3.2 for 64-bit PCs Hrayr. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685726: linux-image-3.2.0-3-amd64: return error when trying
Yeah, Bug is not completely disappeared, my test was done in new formatted partition, which was almost free, and no any error was appeared for image 160Gb. But when I tried to format 160Gb image file on the other machine, where the 2Tb partition is full more than 80% and fragmented, I could reproduce the bug. I'm not sure that these facts are directly connected to bug reproduction, but doing few test on different machines, I'm able to reproduce the error. >> This doesn't include any of the changes that were >> expected to fix this bug, as you did not report that you had tested them. Yeah, I haven't chance to compile and test the new kernel due to lack of time:( Hrayr > On Wed, 2012-11-07 at 16:50 +0400, hr...@infotech.am wrote: >> The problem solved in Debian Wheezy for kernel >> >> linux-image-3.2.0-4-amd64 3.2.32-1 amd64 Linux 3.2 for 64-bit PCs > > Are you sure? This doesn't include any of the changes that were > expected to fix this bug, as you did not report that you had tested > them. It does have other bug fixes for ext4, though. > > Ben. > > -- > Ben Hutchings > The program is absolutely right; therefore, the computer must be wrong. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680487: bug for formating big size file images
Package: unidentified (can be kernel, fs-tools, or other) When I'm trying to format 200Gb empty file image, with the following command: "mkfs -t ext4 ./file.img" (file image was created by the following command: "dd bs=1M count=200k if=/dev/zero of=file.img" ) after some period ot time it is return such messages [50969.139244] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #19922947: comm mkfs.ext4: bad extent address lblock: 303, depth: 2 pblock 0 [50969.139378] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #19922947: comm mkfs.ext4: bad extent address lblock: 304, depth: 2 pblock 0 [50969.139510] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #19922947: comm mkfs.ext4: bad extent address lblock: 305, depth: 2 pblock 0 [50969.139643] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #19922947: comm mkfs.ext4: bad extent address lblock: 306, depth: 2 pblock 0 [50969.139776] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #19922947: comm mkfs.ext4: bad extent address lblock: 307, depth: 2 pblock 0 .. the problem is not discovered with small image files, (f.x. <10Gb) I am using Debian Wheezy 3.2.0-2-amd64 #1 SMP Mon Jun 11 17:24:18 UTC 2012 x86_64 GNU/Linux no any patches are installed, all system by default installation. with debian Squeeze no such poblem was discovered. Hrayr. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685726: linux-image-3.2.0-3-amd64: return error when trying to format image file (mkfs -t ext4 file.img)
> On Fri, 2012-08-24 at 03:30 +0400, Hrayr Grigoryan wrote: >> Package: src:linux >> Version: 3.2.23-1 >> Severity: critical >> Tags: lfs >> Justification: causes serious data loss >> >> Dear Maintainer, >> >>When I'm trying to format file image with the command "mkfs -t ext4 >> file.img", it returns the following errors >> [ 142.328065] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: >> inode #12: comm mkfs.ext4: bad extent address lblock: 1022, depth: 2 >> pblock 0 >> [ 142.328387] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: >> inode #12: comm mkfs.ext4: bad extent address lblock: 1023, depth: 2 >> pblock 0 >> [ 142.328699] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: >> inode #12: comm mkfs.ext4: bad extent address lblock: 9254, depth: 2 >> pblock 0 >> [ 142.329018] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: >> inode #12: comm mkfs.ext4: bad extent address lblock: 1057, depth: 2 >> pblock 0 > > So you have an ext4 filesystem in file.img, on top of an ext4 filesystem > on /dev/sdb1? yes, all are ext4, no other file systems I have on that machine. > >>The problem visible only for big images f.x. 160Gb and more. >>I did the tests on different hardwares, but result the same. > [...] > > How is test.img created, before you run mkfs? Is it a sparse file or > does it have all data blocks allocated? No it is not sparse file, test.img was created with the following command dd if=/dev/zero of=test.img bs=1M count=160k > Have you tested this on any other kernel versions (earlier or later)? Yes, I have tested with the earlier versions, all earlier versions of 3.x.x kernels have this bug. Hrayr. > > Ben. > > -- > Ben Hutchings > Experience is what causes a person to make new mistakes instead of old > ones. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685726: ext4 bug for kernel linux-image-3.2.0-4-amd64 (3.2.39-2).
Today I have upgraded the kernel, now it is linux-image-3.2.0-4-amd64 (3.2.39-2). I think we have to reopen the bug, because it seems that the bug is not solved but just suppressed the warning messages. It is not just my thoughts; everyone can make sure executing couple of command. df ( will show the free space of partition, f.x. 200GB free) dd /dev/zero of=IMG_FILE bs=1M count=128k(will create image file, with size 128GB) df ( now we can see that the partition free space is 72GB, because we have 128GB image file on it) mkfs -t ext4 IMG_FILE(will format image file, without any error messages or warnings!!!) df ( after the formatting process is finished, "df" will show that we have 200GB free space, and "ls -al" will show that we also have file IMG_FILE on the partition, with the size 128GB!!!) This effect is exactly the same as it was before, but with one small difference: the error messages suppressed, and we haven't chance to see errors. It is worst. We have the bug, but haven't error messages. Please take into account that I havent created the "sparse" file, in the case of "sparse file" it is normal when you have 128 GB file on 200 GB partition and the command "df" is show that 200 GB is still free. Hrayr. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#304457: Debuggers
Reviews popular releases picks http://img444.imageshack.us/my.php?image=qyco5.png because different databases -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328163: engine or
pages after happened easytouse tool that http://img444.imageshack.us/img444/2514/lpbp7.png performed tasks openclose go back forward -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#685726: linux-image-3.2.0-3-amd64: return error when trying to format image file (mkfs -t ext4 file.img)
Package: src:linux Version: 3.2.23-1 Severity: critical Tags: lfs Justification: causes serious data loss Dear Maintainer, When I'm trying to format file image with the command "mkfs -t ext4 file.img", it returns the following errors [ 142.328065] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 1022, depth: 2 pblock 0 [ 142.328387] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 1023, depth: 2 pblock 0 [ 142.328699] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 9254, depth: 2 pblock 0 [ 142.329018] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 1057, depth: 2 pblock 0 The problem visible only for big images f.x. 160Gb and more. I did the tests on different hardwares, but result the same. -- Package-specific info: ** Version: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-3-amd64 root=UUID=7d0da86e-f774-4008-87fb-1a120de8c5bf ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 142.293445] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 928, depth: 2 pblock 0 [ 142.293765] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 929, depth: 2 pblock 0 [ 142.294084] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 930, depth: 2 pblock 0 [ 142.294417] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 931, depth: 2 pblock 0 [ 142.294731] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 932, depth: 2 pblock 0 [ 142.295053] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 933, depth: 2 pblock 0 [ 142.295375] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 934, depth: 2 pblock 0 [ 142.295686] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 935, depth: 2 pblock 0 [ 142.296010] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 936, depth: 2 pblock 0 [ 142.296333] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 937, depth: 2 pblock 0 [ 142.296648] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 938, depth: 2 pblock 0 [ 142.297005] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 939, depth: 2 pblock 0 [ 142.297302] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 940, depth: 2 pblock 0 [ 142.297619] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 941, depth: 2 pblock 0 [ 142.297943] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 942, depth: 2 pblock 0 [ 142.298268] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 943, depth: 2 pblock 0 [ 142.298591] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 944, depth: 2 pblock 0 [ 142.298899] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 945, depth: 2 pblock 0 [ 142.299221] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 946, depth: 2 pblock 0 [ 142.299539] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 947, depth: 2 pblock 0 [ 142.299861] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 948, depth: 2 pblock 0 [ 142.300164] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 949, depth: 2 pblock 0 [ 142.300486] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 950, depth: 2 pblock 0 [ 142.300798] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad extent address lblock: 951, depth: 2 pblock 0 [ 142.301110] EXT4-fs error (device sdb1): ext4_ext_map_blocks:3769: inode #12: comm mkfs.ext4: bad
Bug#203211: Increaes your size and stamina today.
Dont be envious of your buddies with huge equipment you can too. http://www.serjuowq.com/ Hit her G-spot every time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
