Bug 192593

Summary: All files/folders in Home folder disappear when updating kernel
Product: [Fedora] Fedora Reporter: adrian <adrian11h>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: pfrields, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-11-24 22:51:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description adrian 2006-05-21 14:44:26 UTC
Description of problem: When updating from kernel vmlinuz-2.6.15-1.2054_FC5 to
kernel vmlinuz-2.6.16-1.2111_FC5 all files and folders in my home folder
disappeared from view although the users still appeared in the Users & Groups
application. When I logged back into kernel 2.6.15-1.2054 my files were all
still there. I had to move all files from the Home partition to the /root
partition then reboot into kernel 2.6.16-1.2111_FC5. Then I had to delete all
users and recreate them to regain home folders. Then copy all the files back to
Home partition.


Version-Release number of selected component (if applicable):
vmlinuz-2.6.16-1.2111_FC5


How reproducible:


Steps to Reproduce:
1.add any file to home folder
2.update from kernel vmlinuz-2.6.15-1.2054_FC5 to kernel vmlinuz-2.6.16-1.2111_FC5
3.
  
Actual results: Files in home folder disappear


Expected results: 


Additional info:

Comment 1 Dave Jones 2006-05-22 19:24:03 UTC
what filesystem are you using ?


Comment 2 Dave Jones 2006-10-17 00:07:15 UTC
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Comment 3 Dave Jones 2006-11-24 22:51:59 UTC
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.

Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.

If you can reproduce this bug after installing all the
current updates, please reopen this bug.

If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.

Thank you.