Skip to contentSkip to conversation

Problem with ufs nextstep in 2.6.18 (debian)

DISCUSSION Dale Amon 1 participant 2 messages Apr 15, 2007

lore
Share & tools
lore

Dale Amon

author
#0 lore raw

I recently noticed that I can no longer read my images of NeXTstep floppies on certain machines. All are running an up to date etch distribution but the difference between where I can read or not read seems to be the linux version. On a 2.6.18 machine:

# mount -t ufs -o ro,ufstype=nextstep,loop nextfloppy-fd0a.ufs /floppy
# ls /floppy
ls: reading directory /floppy: Input/output error

On a 2.6.13 machine it still works fine:

# mount -t ufs -o ro,ufstype=nextstep,loop nextfloppy-fd0a.ufs /floppy
# ls /floppy/
private
# ls /floppy/private
Drivers

Have there been any recent changes that would cause a breakage in this area?

author
#1 lore raw

The error also happens in 2.6.19, same as in 2.6.18. I extracted this from syslog:

Apr 17 00:14:08 kdev kernel: loop: loaded (max 8 devices)
Apr 17 00:14:15 kdev kernel: UFS-fs error (device loop0): ufs_check_page: bad entry in directory #2: directory entry across blocks - offset=356, rec_len=668, name_len=19
Apr 17 00:14:15 kdev kernel: UFS-fs error (device loop0): ufs_readdir: bad page in #2