Quoting Phillip Susi (ps...@ubuntu.com):
>
> That is very odd... what happens if you manually try running fsck -N
> on this partition?
Well, that revealed what's going on.
west ~# fsck -N /dev/sda1
fsck from util-linux 2.25.1
[/sbin/fsck.vfat (1) -- /media/vfat-a1] fsck.vfat /dev/sda1
west ~# fsck -N /dev/sda2
fsck from util-linux 2.25.1
[/sbin/fsck.ext4 (1) -- /westw] fsck.ext4 /dev/sda2
west ~#
whereas on wheezy I got
west ~# fsck -N /dev/sda1
fsck from util-linux 2.20.1
[/sbin/fsck.ext3 (1) -- /westj] fsck.ext3 /dev/sda1
west ~# fsck -N /dev/sda2
fsck from util-linux 2.20.1
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 /dev/sda2
west ~#
And I recognised "/media/vfat-a1" as something I wrote years ago.
For various reasons, some historical, my /etc/fstab looks like:
--8<------
LABEL=john01 / ext3 errors=remount-ro 0 1
LABEL=john04 none swap sw 0 0
LABEL=john03 /home ext3 defaults 0 2
LABEL=john02 /westw ext4 defaults 0 2
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto,nodev,noexec,nosuid 0 0
[...]
# miscellaneous caddies
UUID=2013-1111 /media/lulu02 vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
LABEL=lulu03 /media/lulu03 ext3 rw,user,noauto,nodev,noexec,nosuid
0 0
LABEL=lulu04 /media/lulu04 ext3 rw,user,noauto,nodev,noexec,nosuid
0 0
LABEL=lulu05 /media/lulu05 ext3 rw,user,noauto,nodev,noexec,nosuid
0 0
[...]
# miscellaneous USB sticks, SD cards, MP3 players
UUID=2009-1001 /media/biolinux4g vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
UUID=2009-0301 /media/elite512 vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
# built-in slot
/dev/mmcblk0p1 /media/slot vfat
rw,utf8,tz=UTC,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027
0 0
# foreign sticks and cards
/dev/sda1 /media/vfat-a1 vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
/dev/sda /media/vfat-a vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
/dev/sdb1 /media/vfat-b1 vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
/dev/sdb /media/vfat-b vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
/dev/sdc1 /media/vfat-c1 vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
/dev/sdc /media/vfat-c vfat
rw,utf8,shortname=lower,user,noauto,nodev,noexec,nosuid,fmask=137,dmask=027 0 0
--8<------
If you're wondering why the last paragraph starts at /dev/sda1, it's
because my hard drives (I'm still on PATA drives) used to be mounted
on /dev/hda... and so the first stick/caddy plugged in would appear
as /dev/sda1 (or /dev/sda if the filesystem was not in a partition).
I've now observed that my box running sid does both: it fscks
/dev/sda1 and then emits the same messages as jessie before it's
cleared a moment later. (I grabbed a photograph.)
So the problem now seems to be: why does sid bother with an fstab
entry that has "0" at the end, and why does jessie apparently throw
away the entry that has "1" at the end in favour of the second entry?
Would I be correct in guessing that the zero logical sector size comes
from picking up a number from a FAT-ty location that contains zero in
a linux partition.
Thanks for all your help in tracking this down.
Cheers,
David.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
