On 11/23/05, Andrew Morton <[email protected]> wrote:
> Bret Towe <[email protected]> wrote:
> >
> > while doing a pvmove to get some data off of a drive that was starting to fail
> > i did a refresh on a nfs mount from a client and the server
> > doing this pvmove got the following crash in dmesg
> > and it happened pvmove didnt make any progress any more
> > after a reboot so i could try resuming pvmove it would crash on
> > fsck of one of the lvm partitons i finally got it to boot correctly after
> > running a livecd resuming the pvmove from there without even
> > trying to fsck
> >
> > the kernel that did this orignally i had named 2.6.14-git11.5
> > which for me means i synced to the git tree before the -git12 snapshot
> > had been made i also booted back to 2.6.13.3 to see if it worked
> > but it gave similiar crash i forgot to take a picture of ether of those
> > crashs at boot but solving this other crash would prob prevent
> > the other from happening
> >
> > and no before you ask i do not intend to repeat it :)
> > hopefully somethin can be made of this
> >
>
> Are you using 4k stacks or 8k?
CONFIG_4KSTACKS=y
so says the .config
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
