Bug 492347 - "mount -o remount" does not work with crypto devices mounted by mount.crypt
Summary: "mount -o remount" does not work with crypto devices mounted by mount.crypt
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pam_mount
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Till Maas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-26 15:19 UTC by Bill Nottingham
Modified: 2014-03-17 03:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-13 22:46:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bill Nottingham 2009-03-26 15:19:12 UTC
Description of problem:

pam_mount now writes the following in /etc/mtab:

/dev/sdb1 /home/notting crypt defaults 0 0

This makes 'mount -o <some option>,remount /home/notting' fail - it tries to operate on /dev/sdb1 (which fails). If you pass the actual device-mapper device, that also fails due to that device not being in fstab or mtab.

It can be made to work by passing "mount -i ...", so that it doesn't actually try to call mount.crypt for the remount.

Version-Release number of selected component (if applicable):

pam_mount-1.20-1.fc11.x86_64

Comment 1 Till Maas 2009-03-26 23:22:15 UTC
I guess the "solution" to the problem is to check for "-o remount" in mount.crypt and only perform the remount of the device-mapper device in this case.

Reported upstream:
https://sourceforge.net/tracker/?func=detail&aid=2715698&group_id=41452&atid=430593

Comment 2 Jan Engelhardt 2009-04-04 21:54:39 UTC
Meh, moving items between trackers changes the URL :-/

https://sourceforge.net/tracker/?func=detail&aid=2715698&group_id=41452&atid=430596

Comment 3 Till Maas 2009-04-13 22:46:12 UTC
This should be fixed in iirc pam_mount-1.22-1.fc11

Btw. what did you need to remount your home directory for?

Comment 4 Bill Nottingham 2009-04-14 16:24:14 UTC
Was playing with noatime/relatime.


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