this is the debian way of the unmounting the root fs:
do_stop () {
[ "$VERBOSE" = no ] || log_action_begin_msg "Mounting root filesystem re
ad-only"
MOUNT_FORCE_OPT=
[ "$(uname -s)" = "GNU/kFreeBSD" ] && MOUNT_FORCE_OPT=-f
# This:
# mount -n -o remount,ro /
# will act on a bind mount of / if there is one.
# See #339023 and the comment in checkroot.sh
mount $MOUNT_FORCE_OPT -n -o remount,ro -t dummytype dummydev / 2>/de
v/null \
|| mount $MOUNT_FORCE_OPT -n -o remount,ro dummydev / 2>/de
v/null \
|| mount $MOUNT_FORCE_OPT -n -o remount,ro /
ES=$?
[ "$VERBOSE" = no ] || log_action_end_msg $ES
}
On 6/15/08, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> Oliver Pinter wrote:
>> this mistake shutdownkor comes out, remount launched because he
>> panics, only Alt+Sysrq+foo works
>
> I'm not sure I follow.
>
> Assuming that :
> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00775.jpg
>
> is the first event of interest, it is hitting an assertion on the
> remount path:
>
> ASSERT_ALWAYS(atomic_read(&mp->m_active_trans) == 0);
>
> in xfs_attr_quiesce.
>
> Are you saying something else happen before this? If so, what?
>
> -Eric
>
>> On 6/15/08, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
>>> Oliver Pinter wrote:
>>>> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00775.jpg
>>>> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00776.jpg
>>>> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00777.jpg
>>>> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00778.jpg
>>>> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00779.jpg
>>>> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00780.jpg
>>>> http://students.zipernowsky.hu/~oliverp/upload/xfs_error/dsc00781.jpg
>>>>
>>>> tainted with: nvidia and madwifi
>>>> kernel: 2.6.25.6 + queue patches (queue head on
>>>> aa8edcb997ff605bd1424630356866b78ef06cdc)
>>>>
>>> What sort of remount were you doing?
>>>
>>> -Eric
>>>
>>
>>
>
>
--
Thanks,
Oliver
|
