Colin,

A couple of things I wanted to mention.

1) In the CD lupin-sysctl is not installed, so in the first reboot the
sysctl hacks are simply not used. The sysvinit scripts are identical.

2) In my case I had to reboot several times in order to get a situation
where I could access the logs, and in a few cases I had more severe
locks and had to use alt+sysrq+r+s+u+b (possibly also hard reboot) and
all that was in vm which has been mistreated in the past. All this to
say that fs corruption might have already been there to begin with and
may or may not be a casue of the locks.

So to summarize it seems that sysctl setting do have an important role
in addressing the original poster error. It is uncertain whether such
sysctl settings do actually help in preventing fs corruption (in hard
reboot scenarios and in normal reboot scenarios). It is uncertain
whether fs corruption is a possible outcome of a normal reboot, but from
your tests it seems not (was that with or without sysctl hacks?).

-- 
wubi install unusable - Buffer I/O error on device loop0
https://bugs.launchpad.net/bugs/204133
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to