ecryptfs team mailing list archive

[Rajeev <rajeeja@xxxxxxxxx>]

My system was restored and I was running Karmic for a week. Now, the
same problem arises. I again tried to follow your steps (below). Can you
please tell me what should be removed or what causes the problem that
should be removed when I'm in the problematic install (mount from disk -
Solution mentioned by Ernst)

I don't think there are packages that provide faulty repos. Also, 'sudo
gedit /ubuntu/ etc/apt/ sources. list' command opens a blank file.

------------------------------------------------
Boot with the liveCD/USB and do:

sudo -s -H
mkdir /media/ubuntu
# system partition:
mount /dev/sda5 /media/ubuntu
#/home partition:
mount /dev/sda7 /media/ubuntu/home
mount --bind /dev/ /media/ubuntu/dev
mount --bind /dev/pts /media/ ubuntu/ dev/pts
mount --bind /dev/shm /media/ ubuntu/ dev/shm
chroot /media/ubuntu
mount -t sysfs sysfs /sys
mount -t proc proc /proc
dhclient

Now, you are in your problematic install.
You can use "sudo aptitude remove ....." to remove a certain package, "sudo
nano /etc/apt/ sources. list" to remove repositories who provide faulty
packages (or sudo gedit /ubuntu/ etc/apt/ sources. list on the host, which is
more convenient for most people), "sudo aptitude install <package>/karmic to
downgrade a package to karmic.

-- 
ecryptfs mount does not support -f (fake mount)
https://bugs.launchpad.net/bugs/443080
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” package in Ubuntu: Triaged
Status in “mountall” package in Ubuntu: Fix Committed
Status in ecryptfs-utils in Ubuntu Karmic: Won't Fix
Status in mountall in Ubuntu Karmic: Fix Committed

Bug description:
Binary package hint: e2fsprogs

When a check is forced the fsck process seems to hang. This was what was displayed on screen:

fsck from util-linux-ng 2.16
/dev/sda5 has been mounted 34 times without being checked, check forced
/dev/sda5: 176................. files (2.3% non-contiguous, 48128710/59556......

I left it running four about half an hour but nothing changed and there was no disk activity the entire time. After a hard reset both sda5 and md0 cleanly mounted.
This leds me to believe that the boot process will hang on every fsck (as this happened twice allready, and it hasn't gone successfully yet) and that an actual check of the filesystem therefore never happens...

Note that sda5 is a normal ext3 filesystem. I also have /dev/md0, but this wasn't checked when it hanged.

ProblemType: Bug
Architecture: amd64
Date: Mon Oct  5 14:52:19 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: vmnet vmci vmmon nvidia
Package: e2fsprogs 1.41.9-1ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: e2fsprogs
Uname: Linux 2.6.31-11-generic x86_64