fat32 partition freezes file browser + other applications and can't write to front of partition.

Bug #164138 reported by Mr.UNOwen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pysdm (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: pysdm

What I did:
1. Split off a portion (a majority) of /media and made a fat32 partition using Partition Editor.
2. Installed Pysdm to have fat32 hard drive mount on startup.

What happened:
1. Whenever I access the partition, the file browser will turn dark for about five seconds and then show contents.
2. Recently I found out it won't let me write to the front of the partition. I'm only able to create files in the folders that I previously created.
3. Some programs such as Banshee which access music from the partition freeze up and need to force close, but works after opening it the second time.
4. (only happened once) under /media the partition showed up twice as PARTITION NAME and PARTITION NAME_2 with PARTITION NAME_2 containing files.

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

Anyone?

Revision history for this message
Jaime Soriano (kronoss) wrote :

Sorry for not answering up to now, but i'm not sure if your problem is given by pysdm. Anyways some more information is needed.

You should also know that pysdm can give problems with the latest relases of ubuntu desktop, as some changes has been done in device configuration (automount in desktop,...) and in fstab files format (UID allowed as file system name in /etc/fstab - it has been patched in CVS #79179 -).

Please make sure your filesystem is sane (fsck) and is being mounted with the options and permissions that you want (mount | grep PARTITION NAME).

Try also to see if the programs that freeze up give some descriptive information running them from a terminal.

And paste here the information that can be useful to diagnostize the problem (/etc/fstab and mount lines about your partition at least).

Changed in pysdm:
status: New → Incomplete
Revision history for this message
Jaime Soriano (kronoss) wrote :
Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

so how do I apply that uuid.patch file?

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

My system is an ATI x800/ 2x Xeon 3.06gh/ 1g ram/ 400g sata
No drivers other than what came with the Ubuntu installation (Gutsy)
Emerald Theme Manager installed
4 work space
Update manager says everything is current

So...... whats going on, are you guys looking into it?

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

I've just attached a screen shot of it.
So it's been some time, are you guys looking into it????

Revision history for this message
Jaime Soriano (kronoss) wrote :

The system behaviour that you are descripting is strange.
More information is needed, please, send your /etc/fstab and the output of the command "mount" after mounting the "problematic" partition and all the other things I said you in my last comment (https://bugs.launchpad.net/ubuntu/+source/pysdm/+bug/164138/comments/2)

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

Ok, I just attached it.

Also I don't quite understand what you mean by [and the output of the command "mount" after mounting the "problematic" partition].

Revision history for this message
Jaime Soriano (kronoss) wrote :

Type "mount" in a terminal and copy here the results when your vfat partition is mounted.
Do you have a user called "adminz"?

Anyway the behaviour of your applications is strange, I'm not sure if it's a fstab problem. Try to set default options in your partition.

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

That's what I got

adminz@adminz-desktop:~$ mount /media/MediaKEEP1
mount: /dev/sda4 already mounted or /media/MediaKEEP1 busy
mount: according to mtab, /dev/sda4 is already mounted on /media/MediaKEEP1

adminz@adminz-desktop:~$ mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda3 on /media type ext3 (rw)
/dev/sda4 on /media/MediaKEEP1 type vfat (rw,noexec,nosuid,nodev,uid=1000)
securityfs on /sys/kernel/security type securityfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

I just opened a file in that partition through terminal with no time delay, but when I click on the drive it still froze for some time. So what would this indicate?

Revision history for this message
Jaime Soriano (kronoss) wrote : Re: [Bug 164138] Re: fat32 partition freezes file browser + other applications and can't write to front of partition.

2008/1/16, Mr.UNOwen <email address hidden>:
> I just opened a file in that partition through terminal with no time
> delay, but when I click on the drive it still froze for some time. So
> what would this indicate?
>

I have no idea, but I don't see anything that indicates that it is a
pysdm problem.

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

So have you guys tried recreating the problem? This has gone for some time as a Undecided incomplete status. Other than the fact I didn't mention the brand of the HD is Seagate, I've given you guys everything else I could think of.

Revision history for this message
Hew (hew) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release (Hardy Heron)? Thanks in advance.

Revision history for this message
Mr.UNOwen (jerry-comp) wrote :

I'm no longer having an issue with bug, but now I'm have trouble with another one: bug: 227553.

Revision history for this message
Hew (hew) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in pysdm:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.