I discovered the triggering reason for the kernel Oops. I can reproduce it like this:
- take a 3TB disk, put it into an old USB dock, which does not understand 3TB disks, and observe how Linux reports (in /proc/partitions) a disk size of about 800GB - put the 3TB disk into a modern USB dock, observe that Linux reports the correct size, and format the disk it to one 2TB and one 1TB partitions (this is probably irrelevant, but that's what I did) - format the 2TB partition as ext2fs - remove the disk, put it into the old USB dock and mount the 2TB partition, which is correctly reported as 2TB long by Linux - write into it a long file: when the size reaches about 800GB Linux oopses the way I have reported -- Francesco Potortì (ricercatore) Voice: +39.050.621.3058 ISTI - Area della ricerca CNR Mobile: +39.348.8283.107 via G. Moruzzi 1, I-56124 Pisa Skype: wnlabisti (entrance 20, 1st floor, room C71) Web: http://fly.isti.cnr.it -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ug6b7-0005hk...@tucano.isti.cnr.it
