Bug 12035

Summary: diskdrake should sanity check the fstab it is about to write
Product: Mageia Reporter: Morgan Leijström <fri>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: Normal Keywords: Triaged
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: drakxtools-16.16-1.mga4.src.rpm CVE:
Status comment:

Description Morgan Leijström 2013-12-18 10:51:57 CET
Description of problem: renders system unbootable, and not easy to fix for even medium advanced users.

During the years there have been many occasions when fstab loose important lines after having configured partitions or nfs mounts.


Version-Release number of selected component: all years including now.

How reproducible: every release... 

Steps to Reproduce: see latest example; bug 12033


I propose: everytime a tool is about to write fstab is should chech there is a line for /.
Also, if it can not find a line for /boot, it should check that a /boot folder exists in /.

That are the most important to at least boot.
As option also check similarly for /home, and possibly also for other folders/partitions that should always exist, like /var, /usr etc.

But just making sure it boots at all make it much easier to fix rest of eventual damage.

Reproducible: 

Steps to Reproduce:
Morgan Leijström 2013-12-18 11:12:07 CET

Summary: drak tools should sanity the fstab it is about to write => drak tools should sanity check the fstab it is about to write

Manuel Hiebel 2013-12-22 20:16:06 CET

Keywords: (none) => Triaged
Assignee: bugsquad => thierry.vignaud

Thierry Vignaud 2013-12-28 16:23:29 CET

Summary: drak tools should sanity check the fstab it is about to write => diskdrake should sanity check the fstab it is about to write

Comment 1 Samuel Verschelde 2015-04-23 13:57:02 CEST
Is this still valid Morgan?

Keywords: (none) => NEEDINFO

Comment 2 Morgan Leijström 2015-04-23 15:54:56 CEST
The proposal is to add some sanity check to automatically catch the most obvious ones each time before fstab is written.

Regardless if or not there currently are no bugs like this.

There have been several, probably still are, and probably will pop up new bugs  rendering system unbootable because fstab got corrupled by draktools.
So far i think i have experienced something every release, tha tis why i got this idea (I am using encryption, lvm, nfs)

So valid: yes like having seat belts.
Samuel Verschelde 2015-04-23 16:00:07 CEST

Keywords: NEEDINFO => (none)
Severity: normal => enhancement