Re: PROBLEM: with NTFS (read-only) after upgrade 2.1.131->2.2.1

Steve Dodd (dirk@loth.demon.co.uk)
Sat, 20 Feb 1999 11:10:25 +0000


Hi,

On Sat, Feb 20, 1999 at 01:30:24AM +0100, Peter Münster wrote:

> 1) Problem with NTFS (read-only) after upgrade 2.1.131->2.2.1
> 2) I used to make backups of my NT-Filesystem with a command like:
> cd /win-nt;find . -newer /etc/backup/sda5.ref ! -type d | \
> tar -c -l -T - -f - | bzip2 >$FILE.$SUF
> After a kernel-upgrade from 2.1.131 to 2.2.1, "find" ends with a
> Segmentation fault, the klogd writes some messages which you can find at
> point 5), and unmounting of /win-nt is no more possible (device busy)

>From the oops below, this looks suspiciously familiar. It happens because
NTFS tries to allocate some memory, fails, but doesn't check the return code.
That's fixed in 2.2.1-ac6, or I can send you the patch separately (it should
be in the linux-kernel archives as well). The fact that it runs out of memory
at all is the big problem, you should find that this goes away with the inode
related fixes that are in 2.2.2-pre (and therefore presumably in Alan's
patches as well).

> Trying to open MFT
> (Another question: what does this mean, "Trying to open MFT"?)

It's just debug -- I thought that was only printed if you compiled ntfs
with -DDEBUG, but obviously not. Don't worry about it :)

Did you ever see these problems with 2.1.131 and below? Just curious..

S.

-- 
There was a young man of St. John's
Who wanted to bugger the swans.
        But the loyal hall porter
        Said, "Pray take my daughter!
Those birds are reserved for the dons."    

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/