I'm probably just an idiot but I've got an odd problem:

I've been trying to figure out why /media/mmc1 is mounted read-only... I figured I did something stupid. But testing shows I can edit anything on the mmc UNTIL I run the file manager once. After that, I can no longer edit any files and the filesystem seems to be read-only.

Anybody ever have that happen? What have I done wrong?

Brad.

I don't see that behavior. Can you give us more info about your configuration?
I have a 1GB card which I partitioned from a linux PC.
ls shows it owned by user but group:root . I'm not sure if that's normal

the line in /etc/fstab is:

What does yours look like?

Should have posted more info, sorry. My /etc/fstab entry is identical, and I have the same permissions on /media/mmc1.

Which is what you'd expect, right? If the fstab or the base permissions were incorrect I'd never be able to edit any file at any time, not just after the file manager ran once.

I am using mm-unionfs, so perhaps that's the problem?

(configuration for mm-unionfs is almost identical to the one described here)

Ok, so further testing shows it's only a problem when the MMC card has a mmc-unionfs union on it (if I use the stock 64MB partition with a single vfat partition I'm fine). Looks like a bug or (more likely) I've messed up the configuration somehow, though it seems ok...

Brad.

I too am running unionfs and my partitions are as follows:

Partition1 is approx 128 MB formatted as FAT32 and it's mounted on /media/mmc1
Partition2 is approx 872 MB formatted as ext2 and it's mounted on /media/mmc2
Partition3 is approx 24 MB formatted as linux swap

The swap is activated with that load monitor tool and the device is /dev/mmcblk0p3

My mmc-union directory is on mmc2 and contains the following directories:
#home#user and #var#lib#install

You don't want to use mmc1 (FAT) for your union-fs.

I say approx above because my partitioning program (gparted in FC5) rounds to the nearest cylinder boundry.

If I understand the comment, you're saying I shouldn't setup a union on mmc1, correct? If that's the concern, I'm not.

In fact my configuration looks almost identical to yours:

Partition #1 64MB VFAT
Partition #2 424MB (contains #home#user and #var#lib#install)
Partition #3 24MB swap (mounted at boot)

I assume you've enabled unionfs at boot? If so, have you ever tried to turn it off? (via "mmc-unionfs disable-boot") Doesn't seem to work or I'm misunderstanding how things work.

I reboot the 770 and my unions are still mounted and all the software is installed. Kinda odd.

I'm going to mess around with the stock 64MB card a little, but it looks like I'd done something stupid.

Thanks for the help,

Brad.

If your partition2 is ext2 and not fat then we're almost identical.

I've add sym-links for Root -> / and Home -> /home/user in MyDocs so I can browse the whole filesystem.

Hmmmm... when you say you can't edit any files on mmc1, what do you mean? can you delete a file? create a new file? copy a file to that directory?

I'm running out of ideas

It is indeed (thought I'd added that, sorry)

It appears that if I run the file manager, /media/mmc1 gets mounted read only.

Before I run the file manager, I can open an xterm and vi files, delete them, copy them, everything works as expected.

But once I'm in the file manager, attempting to delete says "unable to delete" or creating a folder says "not allowed". Viewing the details on the Memory card shows that it's NOT read only.

After I exit the file manager and attempt to delete a junk file (one I created just before I ran the file manager) from an xterm I get "rm: unable to remove 'mm': Read-only file system".

Not even root can delete files from /media/mmc1.

Seems crazy since unionfs doesn't use the first partition.

Of course using the USB cable to transfer files works just fine...

Odd, eh?

Brad.

Are you running the latest firmware? Version 5.2006.13-7

BanditRider-

Yup. What self-respecting geek isn't?

Again, thanks for your input. I seemed to have solved the problem, though it still bothers me. I simply reformatted the first partition with "mkfs.vfat" and now everything works.

As odd as it sounds, it's like the contents of the filesystem caused file manager to remount the filesystem as readonly. I do notice I have less directories on the partition now, as before I must have deleted a file while mounted on an XP machine (I had a recycled and system information folders).

Anyways, thanks for the help.

Brad.

Excellent.

I don't let Windows near my 700.
I run strictly Fedora Core 5.