On Sat, Jun 1, 2024, at 11:06 AM, Patrick Dupre via users wrote:
> Hello,
>
> With ext4 filesystems, I used to set
>
> ext4noauto,errors=remount-ro1 2
>
> in the fstab.
>
> With btrfs FS
> it does not like the option errors=remount-ro
That is an ext
e via users
wrote:
>
> Hello,
>
> With ext4 filesystems, I used to set
>
> ext4noauto,errors=remount-ro 1 2
>
> in the fstab.
>
> With btrfs FS
> it does not like the option errors=remount-ro
> mount: /mnt/backup_2: wrong fs type, bad option, bad sup
Hello,
With ext4 filesystems, I used to set
ext4noauto,errors=remount-ro1 2
in the fstab.
With btrfs FS
it does not like the option errors=remount-ro
mount: /mnt/backup_2: wrong fs type, bad option, bad superblock on /dev/sdc5,
missing codepage or helper program, or other error
El 23/5/24 a las 21:28, Mike Wright escribió:
(...)
The other thing I don't understand
It's what I have to write in the fstab
to tell you that when you start...
Also start a partition: /sda7...
which is not /home...
If you could tell me
that I have to write with the mount command
t
On Fri, Jul 7, 2023 at 12:39 AM ToddAndMargo via users <
users@lists.fedoraproject.org> wrote:
> HI All,
>
> Is there a GUI for settin up a new
> drive in fstab? Or do we still need to
> use to old one (vi)?
>
Gnome Disk Utility, aka Disks. Select a storage device a
On Fri, Jul 7, 2023 at 6:16 AM Patrick O'Callaghan
wrote:
On Thu, 2023-07-06 at 20:39 -0700, ToddAndMargo via users wrote:
HI All,
Is there a GUI for settin up a new
drive in fstab? Or do we still need to
use to old one (vi)?
IMHO a GUI would be overkill. It's a text file wi
Plus the gui would be useless unless it had all of the knowledge of
all types of fses and what options were valid.
And coding that into a fstab gui program correctly seems like a
massive undertaking with all of the details. so it would likely be a
mess.
I saw a gui to manage /etc/groups years
On Thu, 2023-07-06 at 20:39 -0700, ToddAndMargo via users wrote:
> HI All,
>
> Is there a GUI for settin up a new
> drive in fstab? Or do we still need to
> use to old one (vi)?
IMHO a GUI would be overkill. It's a text file with a clear structure.
Besides, you sometimes
ToddAndMargo composed on 2023-07-06 20:39 (UTC-0700):
> Is there a GUI for settin up a new
> drive in fstab? Or do we still need to
> use to old one (vi)?
Any plain text editor with superuser permission can edit /etc/fstab, including
adding new entries.
--
Evolution as taught in publi
HI All,
Is there a GUI for settin up a new
drive in fstab? Or do we still need to
use to old one (vi)?
Many thanks,
-T
--
~~~
Having been erased,
The document you're seeking
Must now be re
orian Rosse.
From: Dorian ROSSE
Sent: Wednesday, June 21, 2023 10:21:57 AM
To: Community support for Fedora users
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the b
ROSSE.
From: Dorian ROSSE
Sent: Tuesday, June 20, 2023 11:50:38 AM
To: Community support for Fedora users
Subject: RE: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hello ever
__
De : Dorian ROSSE
Envoyé : lundi 5 juin 2023 17:39
À : Community support for Fedora users
Objet : Re: blkid fully broken too chroot has losen sense in addition fstab has
received an update not smart and luckily locate works with type the button star
Dear Eyal,
After have tried mount without option
users@lists.fedoraproject.org
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hi Dorian,
On 05/06/2023 18.39, Dorian ROSSE wrote:
> Hello everybody and the team fedora,
>
>
understand what you are
saying. Also you may want to give a shorter subject.
However the above three attempts at mounting are incorrect.
'mount -a' asks to mount everything in /etc/fstab and does not expect
the arguments you give.
'mount -o' requires an option, f
ubject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hello everybody and the team fedora,
Although i can't find the dependancies with dnf or yum the installer fedora
find many skeleton o
Rosse.
From: Dorian ROSSE
Sent: Tuesday, May 30, 2023 1:40:17 PM
To: Community support for Fedora users
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hello everybody and the
_
From: Dorian ROSSE
Sent: Monday, May 29, 2023 11:38:43 AM
To: Community support for Fedora users
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hello everybody and the team fedo
this will be repaire after few time
Regards.
Dorian Rosse.
From: Dorian ROSSE
Sent: Friday, May 26, 2023 1:19:25 PM
To: Community support for Fedora users
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not
n addition fstab
has received an update not smart and luckily locate works with type the button
star
I don't care about your story so i am here for the IT
Dorian Rosse.
From: John Pilkington
Sent: Thursday, May 18, 2023 10:40:08 PM
To: users@lists.fedoraproje
I don't care about your story so i am here for the IT
Dorian Rosse.
From: John Pilkington
Sent: Thursday, May 18, 2023 10:40:08 PM
To: users@lists.fedoraproject.org
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has receiv
On 18/05/2023 20:49, Mike Wright wrote:
On 5/18/23 05:21, Dorian ROSSE wrote:
Hello everybody and the team fedora,
blkid fully broken too chroot has losen sense in addition fstab has
received an update not smart so it has losen a lot of part and luckily
locate works without type the button
On 5/18/23 05:21, Dorian ROSSE wrote:
Hello everybody and the team fedora,
blkid fully broken too chroot has losen sense in addition fstab has received an
update not smart so it has losen a lot of part and luckily locate works without
type the button star finally thanks you in advance to
Dorian ROSSE composed on 2023-05-18 12:21 (UTC):
> blkid fully broken too chroot has losen sense in addition fstab has received
> an update not smart so it has losen a lot of part and luckily locate works
> without type the button star finally thanks you in advance to repair whole,
Pl
Hello everybody and the team fedora,
blkid fully broken too chroot has losen sense in addition fstab has received an
update not smart so it has losen a lot of part and luckily locate works without
type the button star finally thanks you in advance to repair whole,
Have a nice week,
Regards
On Mon, May 15, 2023 at 6:32 AM Dorian ROSSE wrote:
> sudo mount -o /dev/sda4 /boot/dos_4
> mount: /boot/dos_4: impossible de trouver UUID=9a71295a-04.
First, "-o" requires options, so the command is not valid.
Second, "impossible de trouver" appears to be "can't find", which
would suggest there
hello everybody and the team fedora,
i happen many errors for mount many part although this step for restore few
systems naturally i have use clonezilla instead a software by acronis so the
parts fedora are keep luckily thus i attach in attachment the file fstab and i
paste below many errors
systemd override or else put a line in
/etc/fstab just as in the days before systemd, and the systemd unit will
respect the size option there.
But, that line in /etc/fstab can do the job on its own, so what's the point of
enabling the tmp.mount unit?
Putting a line in /etc/fstab is a funct
a
> line in /etc/fstab just as in the days before systemd, and the systemd unit
> will respect the size option there.
>
> But, that line in /etc/fstab can do the job on its own, so what's the point
> of enabling the tmp.mount unit?
Putting a line in /etc/fstab is a fun
If I want to use a tmpfs for /tmp, I can just enable the systemd tmp.mount unit
and get the default size limit of 1/2 of memory. If I want to reduce that
limit, I either have to fiddle with a systemd override or else put a line in
/etc/fstab just as in the days before systemd, and the systemd
On Mon, 2022-09-05 at 11:06 -0300, George N. White III wrote:
> For every person who reports a problem like this there are dozens if not
> hundreds
> who never report the problem. Many will discover outdated or incorrect
> advice from the internet.
> Some will decide that linux doesn't work and
hols
> wrote:
> >>>>
> >>>> I have added a line to /etc/fstab:
> >>>> /dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0
> >>>>
> >>>> I have run "systemctl daemon-reload"
> >>>>
On 9/3/22 10:21 PM, Robert Nichols wrote:
On 8/20/22 6:23 PM, Robert Nichols wrote:
On 8/20/22 4:56 PM, Barry wrote:
On 20 Aug 2022, at 19:16, Robert Nichols wrote:
I have added a line to /etc/fstab:
/dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0
I have run
On 9/3/22 21:21, Robert Nichols wrote:
This is getting annoying.
If you haven't already, open a Bugzilla against it.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Co
On 8/20/22 6:23 PM, Robert Nichols wrote:
On 8/20/22 4:56 PM, Barry wrote:
On 20 Aug 2022, at 19:16, Robert Nichols wrote:
I have added a line to /etc/fstab:
/dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0
I have run "systemctl daemon-reload"
After a r
On 8/20/22 4:56 PM, Barry wrote:
On 20 Aug 2022, at 19:16, Robert Nichols wrote:
I have added a line to /etc/fstab:
/dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0
I have run "systemctl daemon-reload"
After a reboot, the command "mount /mnt/imgs&quo
> On 20 Aug 2022, at 19:16, Robert Nichols wrote:
>
> I have added a line to /etc/fstab:
> /dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0
>
> I have run "systemctl daemon-reload"
>
> After a reboot, the command "mount /mnt/imgs
I have added a line to /etc/fstab:
/dev/mapper/imgs /mnt/imgs ext4 noauto,noexec,nodev 0 0
I have run "systemctl daemon-reload"
After a reboot, the command "mount /mnt/imgs" still returns the message:
Mount: (hint) your fstab has been modified, bu
On 22/6/21 11:06, Samuel Sieb wrote:
On 2021-06-21 4:29 p.m., Stephen Morris wrote:
On 20/6/21 02:22, Ed Greshko wrote:
On 19/06/2021 21:44, Stephen Morris wrote:
My system has been upgraded from versions without ZRAM. That is the
reason my system has a defined swap
partition on disk.
I don
On 2021-06-21 4:29 p.m., Stephen Morris wrote:
On 20/6/21 02:22, Ed Greshko wrote:
On 19/06/2021 21:44, Stephen Morris wrote:
My system has been upgraded from versions without ZRAM. That is the
reason my system has a defined swap
partition on disk.
I don't see the connection between Video Me
on in fstab
anymore, but is using, in my case, and 8GB swap partition in
/dev/zram0. Does this mean that if I create a swap partition of a
bigger size and specify it in fstab it will be ignored?
Ignored? No. But not primary. e.g.
[egreshko@meimei ~]$ swapon
NAME TYPE SIZE USED PRIO
hirley wrote:
> >>> One of the first things I did after installing F34 is disable
> >>> swap-on-zram:
> >>>touch /etc/systemd/zram-generator.conf
> >>> and define a swap partition in fstab.
> >>
> >> Why?
>
> I don't se
On Mon, Jun 21, 2021 at 10:51 AM Barry Scott wrote:
>
> The SSDs are a lot slower than compressing a page into RAM.
>
> There was extensive discussion on the Fedora Devel list when this change was
> proposed.
>
> Personally I was convinced that this change is an improvement for any system
> that
-generator.conf
and define a swap partition in fstab.
Why?
I don't see how that's an answer to why you would disable zram.
Especially when your later reply shows that you're not really even using
the disk swap anyway.
___
users mailin
erver is running on Raid-1 SSDs with 64GB of RAM
>
> Bill
>
> On 6/21/2021 3:41 AM, Samuel Sieb wrote:
>> On 6/20/21 7:25 PM, Bill Shirley wrote:
>>> One of the first things I did after installing F34 is disable swap-on-zram:
>>>touch /etc/systemd/zram-
[0 07:20:34 root@yoda33 ~]$ swapon
NAME TYPE SIZE USED PRIO
/dev/sdc1 partition 64G 9.7M 300
/dev/sdd1 partition 64G 9.4M 300
[0 03:06:33 root@yoda33 ~]$ uptime
03:08:30 up 23 days, 18:33, 2 users, load average: 0.01, 0.01, 0.00
On 6/21/2021 4:18 AM, Ed Greshko wrote:
On 21/06/2021 1
On 21/06/2021 16:05, Bill Shirley wrote:
The server is running on Raid-1 SSDs with 64GB of RAM
I suppose the follow-up question would be are you seeing the swap partition
actually being used?
Does "swapon" show it has been used?
--
Remind me to ignore comments which aren't germane to the th
fstab.
Why?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https
On 6/20/21 7:25 PM, Bill Shirley wrote:
One of the first things I did after installing F34 is disable swap-on-zram:
touch /etc/systemd/zram-generator.conf
and define a swap partition in fstab.
Why?
___
users mailing list -- users
One of the first things I did after installing F34 is disable swap-on-zram:
touch /etc/systemd/zram-generator.conf
and define a swap partition in fstab.
Bill
On 6/19/2021 12:45 AM, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34 under a vm,
On 19/06/2021 21:44, Stephen Morris wrote:
On 19/6/21 15:31, Ed Greshko wrote:
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34 under a vm,
that fedora does not have a swap specification in fstab anymore, but is using,
in my
On 19/6/21 15:31, Ed Greshko wrote:
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34
under a vm, that fedora does not have a swap specification in fstab
anymore, but is using, in my case, and 8GB swap partition in
/dev/
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34 under a vm,
that fedora does not have a swap specification in fstab anymore, but is using,
in my case, and 8GB swap partition in /dev/zram0. Does this mean that if I
create a
Hi,
I've noticed when trying remediate performance issues in F34 under
a vm, that fedora does not have a swap specification in fstab anymore,
but is using, in my case, and 8GB swap partition in /dev/zram0. Does
this mean that if I create a swap partition of a bigger size and specify
On Sun, 2019-08-18 at 08:06 +1000, Cameron Simpson wrote:
> On 17Aug2019 12:01, Patrick O'Callaghan wrote:
> > On Sat, 2019-08-17 at 09:38 +1000, Cameron Simpson wrote:
> > > Really, all you need to do is to remove the /var fstab entry, umount
> > > the
> >
On 17Aug2019 12:01, Patrick O'Callaghan wrote:
On Sat, 2019-08-17 at 09:38 +1000, Cameron Simpson wrote:
Really, all you need to do is to remove the /var fstab entry, umount
the
existing /var mount, rsync /newvar BACK INTO the stub /var mountpoint
which is there, scrub /newvar.
/var c
On Sat, 2019-08-17 at 17:59 +0200, francis.montag...@inria.fr wrote:
> Hi.
>
> On Sat, 17 Aug 2019 12:01:01 +0100 Patrick O'Callaghan wrote:
> > I did finally solve it following the suggestion from
> > francis.montag...@inria.fr (adding rd.break=pre-pivot to the boot line,
> > then remounting /sy
Hi.
On Sat, 17 Aug 2019 12:01:01 +0100 Patrick O'Callaghan wrote:
> I did finally solve it following the suggestion from
> francis.montag...@inria.fr (adding rd.break=pre-pivot to the boot line,
> then remounting /sysroot etc.)
Correction: that was a suggestion of Tony Nelson (thanks for this t
> /var to /newvar with rsync, and now want to mount /newvar as /var on
> > reboot by creating an entry in /etc/fstab. This is it (using /var-tst
> > for testing):
> >
> > /newvar /var-tstext4
> > loop0
ing an entry in /etc/fstab. This is it (using /var-tst
for testing):
/newvar /var-tstext4loop
0 0
That isn't what loop is for. loop is for associating a file with a
device.
What you want is "bind", not "loop
On Fri, 2019-08-16 at 09:20 -0400, Tom Horsley wrote:
> On Fri, 16 Aug 2019 14:11:09 +0100
> Patrick O'Callaghan wrote:
>
> > That was the first thing I tried, but I can't rename /newvar to /var as
> > /var is "in use" and of course can't be unmounted.
>
> That sort of thing is what live media wa
gt; > > > Can you boot from live media? If so, you could just rename
> > `/newvar` to
> > > > `/var` and edit fstab.
> > > I may have to do that as /var is too central to booting even in
> > single-
> > > user mode.
> >
> > I wo
d 0 0
> > >
> > > I use this to put /home on a bigger disk than the OS was installed on
> > > (and recover /home from previous installs since /zooty/home hangs around).
> >
> > That "works" (i.e. doesn't give an error and does m
;t give an error and does mount the directory)
...
Of course, I have no idea if something during boot might want
/var prior to even looking at the fstab, so this might not work.
... however the system refuses to boot (SDDM throws an error, then
system reboots). Something doesn't like /var being
On 19-08-16 09:25:36, francis.montag...@inria.fr wrote:
Hi.
On Fri, 16 Aug 2019 14:12:06 +0100 Patrick O'Callaghan wrote:
> On Fri, 2019-08-16 at 09:58 -0300, George N. White III wrote:
>> Can you boot from live media? If so, you could just rename
`/newvar` to
>> `/var`
Hi.
On Fri, 16 Aug 2019 14:12:06 +0100 Patrick O'Callaghan wrote:
> On Fri, 2019-08-16 at 09:58 -0300, George N. White III wrote:
>> Can you boot from live media? If so, you could just rename `/newvar` to
>> `/var` and edit fstab.
> I may have to do that as /var is too
On Fri, 16 Aug 2019 14:11:09 +0100
Patrick O'Callaghan wrote:
> That was the first thing I tried, but I can't rename /newvar to /var as
> /var is "in use" and of course can't be unmounted.
That sort of thing is what live media was invented for :-).
Boot off a live USB stick, mount the system dis
age. I've copied
> > /var to /newvar with rsync, and now want to mount /newvar as /var on
> > reboot by creating an entry in /etc/fstab. This is it (using /var-tst
> > for testing):
> >
> > /newvar /var-tstext4
>
t; > copied /var to /newvar with rsync, and now want to mount /newvar as
> > /var on reboot by creating an entry in /etc/fstab. This is it (using
> > /var-tst for testing):
> >
> > /newvar /var-tstext4
> >
n't give an error and does mount the directory)
...
> Of course, I have no idea if something during boot might want
> /var prior to even looking at the fstab, so this might not work.
... however the system refuses to boot (SDDM throws an error, then
system reboots). Something doesn'
ar on
> reboot by creating an entry in /etc/fstab. This is it (using /var-tst
> for testing):
>
> /newvar /var-tstext4
> loop0 0
>
> but I'm getting:
>
> mount: /var-tst: failed to setup loop device for /new
> /var on reboot by creating an entry in /etc/fstab. This is it (using
> /var-tst for testing):
>
> /newvar /var-tstext4
> loop0 0
>
> but I'm getting:
>
> mount: /var-tst: failed to setup loop
0 0
I use this to put /home on a bigger disk than the OS was installed on
(and recover /home from previous installs since /zooty/home hangs around).
Of course, I have no idea if something during boot might want
/var prior to even looking at the fstab, s
I'm trying to rationalise space by moving my /var directory from its
own partition to /, as currently there's a lot of wastage. I've copied
/var to /newvar with rsync, and now want to mount /newvar as /var on
reboot by creating an entry in /etc/fstab. This is it (using /var-
chose the "setup" package since it consists of numerous
> fundamental system files for which some errors in verification would
> be cause for concern, and got the following on my F27 system:
>
> $ rpm -V setup
> .M... c /etc/fstab
> S.5T. c /etc/printcap
&g
s
fundamental system files for which some errors in verification would
be cause for concern, and got the following on my F27 system:
$ rpm -V setup
.M... c /etc/fstab
S.5T. c /etc/printcap
S.5T. c /etc/profile
.MG.. g /var/log/lastlog
$
i have no problem with files
Hey.
Thanks! Just found the offending lines in the /etc/fstab file on the
nfs server...
The little things..
On Mon, Feb 12, 2018 at 7:38 PM, Rick Stevens wrote:
> On 02/12/2018 10:40 AM, bruce wrote:
>> Hi.
>>
>> I've screwed up a test system. Somehow I've
eed to change to remove them?? files/processes/etc...
Er, "sudo lsof | grep cloud_nfs_" to see if anything's using those mount
points. If not, then I'd assume something like
sudo umount /cloud_nfs_fetch
sudo umount /cloud/nfs_parse
should unmount
Hi.
I've screwed up a test system. Somehow I've managed to "link/attach" 3 dirs
df -h shows
/dev/vda130G 9.0G 19G 33% /
tmpfs 499M 0 499M 0% /dev/shm
/dev/sda296G 274M 280G 1% /cloud_nfs
/dev/sda296G 274M 280G 1% /cloud_nfs_fetch
/dev/sda
On Mon, 13 May 2013 15:01:31 +0800
Ed Greshko wrote:
> > I know shared yum cache, but it's a pet project.
> >
>
> Oh, I see now. I had a difficult time to grok what you're
> getting at since I didn't make a connection with what you are
> trying to do.
>
> Looks like you're trying to shar
On 05/13/13 14:41, Frank Murphy wrote:
> On Mon, 13 May 2013 05:26:52 +0800
> Ed Greshko wrote:
>
>> Well, have you tried removing no_root_squash and re-exporting?
>>
> Same [Errno 13] Permission denied: '/var/cache/yum/18'
>
> I know shared yum cache, but it's a pet project.
>
Oh, I see now.
On Mon, 13 May 2013 05:26:52 +0800
Ed Greshko wrote:
>
> Well, have you tried removing no_root_squash and re-exporting?
>
Same [Errno 13] Permission denied: '/var/cache/yum/18'
I know shared yum cache, but it's a pet project.
--
Regards,
Frank - I check for new mail app. 20min
www.frankly3d
On 05/13/13 05:08, Frank Murphy wrote:
> On Mon, 13 May 2013 03:37:41 +0800
> Ed Greshko wrote:
>
>> On the server what is the contents of /etc/exports?
>>
> /exported_dir
> 192.168.0.1/255.255.255.0(rw,wdelay,sync,no_root_squash)
>
>
>
Well, have you tried removing no_root_squash and re-exportin
On Mon, 13 May 2013 03:37:41 +0800
Ed Greshko wrote:
>
> On the server what is the contents of /etc/exports?
>
/exported_dir
192.168.0.1/255.255.255.0(rw,wdelay,sync,no_root_squash)
--
Regards,
Frank - I check for new mail app. 20min
www.frankly3d.com
--
users mailing list
users@lists.fed
On 05/13/13 00:52, Frank Murphy wrote:
> If I mount the server export on the client in /etc/fstab
>
> or mount "server:/export /mountpoint" it works
>
> but if setup as autofs.nfs on the client
>
> -rw,hard,intr,nolock,rsize=8192,wsize=8192
> se
If I mount the server export on the client in /etc/fstab
or mount "server:/export /mountpoint" it works
but if setup as autofs.nfs on the client
-rw,hard,intr,nolock,rsize=8192,wsize=8192
server:/export
it says [Errno 13] Permission denied: /export/remote_dir
the
unit mounted if present.
>>
>> The fsck is (I believe) controlled independently from noauto
>> by one of the two obscure numbers on the end of the mount
>> line (which may actually be documented in the fstab
>> man page).
>>
> It is, that's what I was me
On 02/26/2013 03:19 PM, Bill Davidsen wrote:
Since these machines hold backup copies of data, hopefully they don't
need to be up immediately. If needed there will be someone present to
supervise, although if the RAID boxes are connected they could be
powered on remotely, manually fsck'd, and mo
Joe Zeff wrote:
On 02/25/2013 12:01 PM, Bill Davidsen wrote:
The time to recover typical issues in a journaled filesystem is minimal,
if the f/s is really borked there will be an admin present during the
boot anyway.
What are the boxes set to do when power is restored after a failure? Stay o
On 02/25/2013 12:01 PM, Bill Davidsen wrote:
The time to recover typical issues in a journaled filesystem is minimal,
if the f/s is really borked there will be an admin present during the
boot anyway.
What are the boxes set to do when power is restored after a failure?
Stay off, turn on, or
es any of these
things you tried work on Fedora 17 or 18 ?
fc1[78] have the "nofail" option in fstab, which on paper does what I want. I
have to set up a test system, or test case on a system, so I can verify that the
result is what I want, but it looks like the logic is what I want
On 24/02/13 06:24, Bill Davidsen wrote:
...
> Yes, that was an attempt to avoid the hang on boot, what I really need
> is more complex, and I may have to put it in rc.local to make it work,
> although I will test on Fedora using the nofail option. As I look at the
> RHEL world, I expect RHEL7 to be
from noauto
by one of the two obscure numbers on the end of the mount
line (which may actually be documented in the fstab
man page).
It is, that's what I was mentioning in the 2nd paragraph, the fsck field
controls the order in which checks are done before mounting, to be sure that
mounts on
uto
by one of the two obscure numbers on the end of the mount
line (which may actually be documented in the fstab
man page).
Using noauto though means it won't mount it at all. You'd
have to do something like put a mount command in /etc/rc.d/rc.local
that could simply fail if the device isn
On 02/23/2013 12:37 PM, Bill Davidsen wrote:
> I thought the 'nofail' option would solve the problem, but that appears
> to be a very recent option, and not in RHEL running on this server.
>
> Any thoughts gratefully accepted, we try to keep vital infrastructure
> running on RHEL rather than Fedor
I have a system used for backups, and when it boots it *may* have any or all of
a number of small hot-swap RAID storage units connected by eSATA. Ideally I
would like the system to fsck and mount these when present, using the UUID=
option in fstab. There's a problem. If the units ar
On Thu, Jun 7, 2012 at 11:51 AM, suvayu ali wrote:
>>>> Has someone manage to have Dropbox to work on F17? I have installed
>>>> it, but I get the following error:
>>>>
>>>> "cannot enable user_xattr in /etc/fstab"
>>>>
>&
On Thu, Jun 7, 2012 at 12:00 PM, Paul Smith wrote:
> On Thu, Jun 7, 2012 at 10:57 AM, suvayu ali
> wrote:
>>> Has someone manage to have Dropbox to work on F17? I have installed
>>> it, but I get the following error:
>>>
>>> "cannot enable user_
On Thu, Jun 7, 2012 at 10:57 AM, suvayu ali wrote:
>> Has someone manage to have Dropbox to work on F17? I have installed
>> it, but I get the following error:
>>
>> "cannot enable user_xattr in /etc/fstab"
>>
>> Any ideas?
>
> A minute of sear
On Thu, Jun 7, 2012 at 11:51 AM, Paul Smith wrote:
> Dear All,
>
> Has someone manage to have Dropbox to work on F17? I have installed
> it, but I get the following error:
>
> "cannot enable user_xattr in /etc/fstab"
>
> Any ideas?
>
A minut
1 - 100 of 166 matches
Mail list logo
