[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#571085: marked as done (no write access in /home reiserfs (encrypted) 2.6.32-2-686)

Your message dated Thu, 6 Jun 2013 00:11:53 +0200
with message-id <20130605221153.GA5444@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #571085,
regarding no write access in /home reiserfs (encrypted) 2.6.32-2-686
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
571085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571085
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.32-2-686 
hello,
I have upgraded kernel to 2.6.32-2-686 from 2.6.26-2-686.
After that, when I boot my laptop (debian lenny) I get the error about no write access to /home.
It's mounted with rw options and it's encrypted from /dev/mapper/dat-home.
After rebooting the system, everything works well without problems, 
but if I switch off my laptop, next time I boot I get the same error. 
Please, could you help me?
thank you
robi

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: