Bug 238880 - On boot; swap file do not allow swapon: No access.
Summary: On boot; swap file do not allow swapon: No access.
Alias: None
Product: Fedora
Classification: Fedora
Component: booty   
(Show other bugs)
Version: 6
Hardware: other
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-03 16:38 UTC by Henning Kvello-Aune
Modified: 2008-05-06 19:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 19:34:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Henning Kvello-Aune 2007-05-03 16:38:51 UTC
I'm not able to find the correct name for my platform: AMD64-PC Fedora 6,
updated 10 min ago. And I can not find a component for booting. 

Description of problem:
When booting I get this message in Norwegian language: 
Aktiverer swap-områder fra /etc/fstab: swapon: 
cannot open /etc/fstab: Ikke tilgang 

I then try to translate to English: 
Activating swap-area from /etc/fstab: swapon: 
cannot open /etc/fstab: No access 

I boot up and run GParted, right-click on: /dev/hda3/ Linux swap 2,96Gb, and
shoose swapon. Then the swap is on. 

My line for swap in /etc/fstab: 
LABEL=SWAP-hda3	swap		swap		defaults	0 	0
The command 'll /etc/fstab': 
-rw-r--r-- 1 root root 1225 mai  3 18:44 /etc/fstab 

I must add: I doubled my swap-file frog 1.5Gb to 3Gb after adding memory chip,
it was 792Mb and now it is 1,5Gb. I think I should have the swap-file double
size of the memory??? 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Henning Kvello-Aune 2007-05-04 14:59:46 UTC
The command as root: swapon -a, does not work either, only turning on the swap
file by the program GParted. 

Comment 2 Bug Zapper 2008-04-04 07:10:49 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 3 Bug Zapper 2008-05-06 19:34:15 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.