Bug 2575 – changes to fstab (mount mmc as /home) ignored on device startup

Bug 2575 - changes to fstab (mount mmc as /home) ignored on device startup


Summary:	changes to fstab (mount mmc as /home) ignored on device startup

Status:	RESOLVED INVALID

Product:	Desktop platform
Component:	startup-shutdown
Version:	4.1.2 (4.2008.36-5)
Platform:	N810 Linux

Importance:	Low normal (vote)
Target Milestone:	---
Assigned To:	Kimmo Hämäläinen
QA Contact:	startup-shutdown-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2007-12-17 13:30 UTC by carbonfreeze
Modified:	2009-01-26 11:13 UTC (History)
CC List:	3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description carbonfreeze (reporter) 2007-12-17 13:30:10 UTC

Recently attempted to use /dev/mmcblk0p1 as /home on n810, unfortunately
/etc/fstab appears to be ignored by the OS during device startup. If I manually
umount & mount the partition with the installed console or via ssh, the
partition is mounted at the correct location.

STEPS TO REPRODUCE THE PROBLEM:
Change mount point of the internal mmc device in fstab.

EXPECTED OUTCOME:
Device /dev/mmcblk0p1 is mounted at the designated location in fstab.

ACTUAL OUTCOME:
Device /dev/mmcblk0p1 is mounted at /media/mmc2 at boot time.

REPRODUCIBILITY:
always

EXTRA SOFTWARE INSTALLED:
gcc4, nano, misc games, python...

OTHER COMMENTS:
firmware build 2007-42-19. Also tested with mount point of /media/mmc-test
(which I created) with same results.

Comment 1 carbonfreeze (reporter) 2007-12-17 13:57:35 UTC

Due to additional issues[1] with this file system, re-created with mkfs.vfat -F
32. Afterwards, fstab settings are not ignored on bootup of OS.

[1]   dmesg noted issues which prompted re-creation of file system:
FAT: Filesystem panic (dev mmcblk0p1)
mmcblk0: rw=0, want=3941462, limit=3932160


Will attempt to transfer all of my data back into the file system to reproduce
the original purpose of this bug report.

Comment 2 carbonfreeze (reporter) 2007-12-17 14:22:31 UTC

(In reply to comment #1)
> Due to additional issues[1] with this file system, re-created with mkfs.vfat -F
> 32. Afterwards, fstab settings are not ignored on bootup of OS.

Or not. After further testing, fstab entries are still ignored.

Comment 3 Andre Klapper maemo.org

2008-12-10 21:48:09 UTC

Is this still an issue in the latest Diablo release (4.2008.36-5)?

Comment 4 carbonfreeze (reporter) 2008-12-10 23:01:52 UTC

Yes, this problem still exists on my n810 on Diablo.

Comment 5 Andre Klapper maemo.org

2008-12-10 23:17:21 UTC

4.2008.36-5 version?

Comment 6 carbonfreeze (reporter) 2008-12-11 02:31:12 UTC

Yes, as delivered by maemo updater.

Comment 7 Kimmo Hämäläinen nokia

2008-12-11 10:29:55 UTC

IIRC, N810 has 'linuxrc' script in /mnt/initfs that does basic file system
mounting. However, the memory cards are removable and must be handled at
run-time, that's why there is a policy daemon called 'ke-recv' doing it.

Comment 8 Andre Klapper maemo.org

2008-12-16 19:10:05 UTC

Kimmo: So is this a WONTFIX as per last comment as it's not possible to boot if
the memory card has been removed?
If not, this sounds like an enhancement to me...

Comment 9 Kimmo Hämäläinen nokia

2008-12-17 10:43:26 UTC

Booting is not a problem, but using fstab (instead of e.g. HAL) for removable
memory cards is just stupid.

Comment 10 Andre Klapper maemo.org

2009-01-20 15:08:05 UTC

"Don't put removeable devices into fstab" makes this a WONTFIX or even INVALID
to me.

Comment 11 Frantisek Dufka maemo.org

2009-01-26 10:56:18 UTC

(In reply to comment #9)
> using fstab (instead of e.g. HAL) for removable
> memory cards is just stupid.

"not supported" may be more accurate explanation ;-)

As long as user doesn't plan to remove the card while device is turned on I
don't see anything stupid. Though, it may be easier and more robust to just
boot from the card https://wiki.maemo.org/Booting_from_a_flash_card and have
complete filesystem there.

Comment 12 Frantisek Dufka maemo.org

2009-01-26 11:13:15 UTC

And BTW, it would be nice to remove /etc/fstab altogether from the device since
it is not used at all and confuses people a lot. If this is not possible then
please remove at least the
/dev/mmcblk0p1 /media/mmc1 ....
line from /etc/fstab since it misleads people into thinking it is actually used
and scenario reported in this bug is possible.

I've seen many confused posts on ITT asking why fstab doesn't work or why
changing filesystem type in that /dev/mmcblk0p1 line does not work.