http://qa.mandrakesoft.com/show_bug.cgi?id=3353

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2003-03-16 07:18 -------
Ah, thank you, I'm sorry, I didn't know I could just substitute cooker packages
on RC2...  Looks like it's gonna work though so I'll mark this as fixed, I still
don't see the bug listed on here but I'll take your word for it, I'm new to this
system.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date: 
description: 
I'm slightly puzzled with this...  Here's my scenario.

I have a computer w/ an Athlon 750MHz, 768M RAM, and 2 60Gb hard drives
connected to a PCI ATA-100 IDE controller
It is dual boot w/ Mandrake Linux 9.1 RC2 and Windows XP Professional
The first drive is setup w/ 4 partitions, 
1) ext3 /boot
2) swap swap
3) ext3 /home
4) ext3 /
The other drive is setup w/ 1 NTFS partition

I have /mnt/windows/ setup as the mount point for the ntfs drive, the fstab line
is--> /dev/hdg1 /mnt/windows ntfs umask=000,iocharset=iso8859-1,ro 0 0

This worked no problem initially, then (I don't know of anything significant
that happened to cause this) all of a sudden when I tried to browse that
directory to add an mp3 to the XMMS playlist the process hung and was given a
'D' ('uninterruptible sleep') status, and I could not kill it.  Doing an ls
/mnt/windows also hung at that point.  I did a umount /mnt/windows and it failed
because the device was busy.  I tried again w/ the -l flag and it kinda worked,
but of course it didn't really unmount it, just removed it from the file
hierarchy so I won't hang any other programs....  Of course a reboot temporarily
fixes this, but after less than a day of uptime it happens again.  I am
currently building a new kernel (2.4.21-pre5) to see if that fixes the problem.

Hope this is useful -- you got a nice distro going

Reply via email to