So, you can not fix a mounted partition. So, make sure to to un-mount with as root. Use the sequence:
As for your partition setup, the EXT4 file system is the default and a more robust system in handling system errors. If you should get past this problem or if you decide to rebuild /dev/sdb1 again, go with EXT4 next time. As for your partition setup on /dev/sda, having 10 partitions is kind of extreme. It looks like you are booting from primary Extended Partition /dev/sda4 which the Windows boot manager will not understand. Be sure to stick with a Linux Partitioning program for this kind of setup. Good Luck.
When the filesystem is mounted at boot time, I got this problem. If I mount the filesystem after boot time, it mounts without any problem.
So I think the filesystem is not the problem but the way it is mounted during boot time.
>When the filesystem is mounted at boot time, I got this problem. If I
>mount the filesystem after boot time, it mounts without any problem.
>So I think the filesystem is not the problem but the way it is mounted
>during boot time.
and the same for the mount command you use.
code blocks take the advanced editor on the web interface.
On 11/10/2012 03:06 AM, jvolkers wrote:
> nrickert;2500049 Wrote:
>> How often do you reboot?
>> I am asking, because there is an apparent ext4 bug that is triggered by
>> frequent mounting or rebooting.
>> ‘EXT4 Data Corruption Bug Hits Stable Linux Kernels’
>> Your symptoms sound a bit similar. I know you said ext3, but I think
>> there’s a lot of common code between ext3 and ext4.
> I boot my system mostly once each day
To trigger that ext4 bug required a very special set of circumstances. First of
all, you needed to unmount the file system using the lazy (-l) option. That is
risky, and you had best know what you are doing. Secondly, you need to shut down
before the users of that file system have exited. The standard system does not
use that option, thus most users are not exposed to that bug.
The “too-soon” boot guess was just that when the developers were trying to
duplicate/analyze the problem. It was wrong.