On Sun, Feb 19, 2023 at 10:06:30PM -0500, Felix Miata wrote:
[...]
> All my installations that use a separate filesystem for /boot/ use EXT2. It
> still
> works as good as ever for such an infrequent use environment, with no way to
> get
> ahead of Grub evolution. :)
There are more reasons
ay's entry referenced this from Launchpad from 2019:
>> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1844012
> Also from Debian on 2023.02.15.
> https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1895219.html
> Playing with this has been.. fun.. I guess. I
on 2023.02.15.
>
> https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1895219.html
>
> Playing with this has been.. fun.. I guess. I found a
> "metadata_csum_seed" culprit in /etc/mke2fs(.)conf. It's in the line
> for ext4 which is what I use.
>
> Saw
ferenced this from Launchpad from 2019:
>
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1844012
Also from Debian on 2023.02.15.
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1895219.html
Playing with this has been.. fun.. I guess. I found a
"metadata_cs
Hi.. This is just regurgitating something related to my coincidentally
referencing several years of GRUB non-boots yesterday. The latest on
this Linux From Scratch thread came into my inbox this morning, and it
just sounds like it might help some Users having booting problems
similar to what I've
:/home/legg# mke2fs -j /dev/hdb1
mke2fs 1.41.3 (12-Oct-2008)
/dev/hdb1 is mounted; will not make a filesystem here!
engineering:/home/legg# umount /dev/hdb1
umount: /dev/hdb1: not mounted
engineering:/home/legg# mke2fs -j /dev/hdb1
mke2fs 1.41.3 (12-Oct-2008)
/dev/hdb1 is mounted; will not make
heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x38ef9d17
Device Boot Start End Blocks Id System
/dev/hdb1 1 24321 195358401 83 Linux
engineering:/home/legg# mke2fs -j /dev/hdb1
mke2fs 1.41.3
, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x38ef9d17
Device Boot Start End Blocks Id System
/dev/hdb1 1 24321 195358401 83 Linux
engineering:/home/legg# mke2fs -j /dev/hdb1
mke2fs
arbitrary values for block size and count, probably
bigger than needed, but not harmful either.
Then try the mke2fs again.
If you want to start over completely, you could try the same command but
with of=/dev/hdb (the whole disk), which will destroy partition
information as well as any partition
, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x38ef9d17
Device Boot Start End Blocks Id System
/dev/hdb1 1 24321 195358401 83 Linux
engineering:/home/legg# mke2fs -j /dev/hdb1
mke2fs
bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x38ef9d17
Device Boot Start End Blocks Id System
/dev/hdb1 1 24321 195358401 83 Linux
engineering:/home/legg# mke2fs -j /dev
should I do, just quit it?
~$ /sbin/mke2fs -c /dev/sda1
mke2fs 1.40-WIP (14-Nov-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
122109952 inodes, 244190008 blocks
12209500 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks
the total blocks, but it is still
running. What should I do, just quit it?
~$ /sbin/mke2fs -c /dev/sda1
mke2fs 1.40-WIP (14-Nov-2006)
This is an old version, and it may be that you hit bug #411838¹ or some
other problem that has been fixed in the meantime. I would definitely
try a newer version
exceeded the total blocks, but it is still
running. What should I do, just quit it?
~$ /sbin/mke2fs -c /dev/sda1
mke2fs 1.40-WIP (14-Nov-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
122109952 inodes, 244190008 blocks
12209500 blocks (5.00%) reserved
Thanks Sven. Will it be any problem if I quit it by pressing Ctr-c? If
I understand it correctly, the mke2fs -c is only check the bad block,
not write or format the disk, right?
By the way, it has not reached the maximum blocks yet, but it seems it
need to run another 3 days to finishe it. I
On 2009-08-09 05:25, hce wrote:
Thanks Sven. Will it be any problem if I quit it by pressing Ctr-c? If
I understand it correctly, the mke2fs -c is only check the bad block,
not write or format the disk, right?
No problem.
--
Scooty Puff, Sr
The Doom-Bringer
--
To UNSUBSCRIBE, email
, but it is still
running. What should I do, just quit it?
~$ /sbin/mke2fs -c /dev/sda1
sda??? Is your boot disk hda?
Is it plugged into a USB 1.1 port?
Also, I wouldn't be surprised if check bad blocks weren't
inordinately slow even on internal disks.
mke2fs 1.40-WIP (14-Nov-2006
Boa tarde,
Sem querer usei o comando mke2fs no hd errado, ele formatou esta partiççao,
tem como desfazer este comando?
Obrigado,
--
Adriano de Souza Barbosa
Msn: [EMAIL PROTECTED]
o comanado que usei foi: #mke2fs /dev/hdc
Em 24/06/07, Adriano Maverick [EMAIL PROTECTED] escreveu:
Boa tarde,
Sem querer usei o comando mke2fs no hd errado, ele formatou esta
partiççao, tem como desfazer este comando?
Obrigado,
--
Adriano de Souza Barbosa
Msn: [EMAIL PROTECTED
Este HD antes estava com duas partições tbem, hdc1 e hdc2
Em 24/06/07, Adriano Maverick [EMAIL PROTECTED] escreveu:
o comanado que usei foi: #mke2fs /dev/hdc
Em 24/06/07, Adriano Maverick [EMAIL PROTECTED] escreveu:
Boa tarde,
Sem querer usei o comando mke2fs no hd errado, ele formatou
O testdisk resolve isso, caso nada mais tenha sido feito após o mke2fs.
Sucesso.
CR
Em 24/06/07, Adriano Maverick [EMAIL PROTECTED] escreveu:
Este HD antes estava com duas partições tbem, hdc1 e hdc2
Em 24/06/07, Adriano Maverick [EMAIL PROTECTED] escreveu:
o comanado que usei foi
. Alternativ kann man auch mit fsck herummurksen.
Während des Formatierens ist die ssh Verbindung abgebrochen.
Mit screen wollte ich versuchen den Dialog mke2fs -cj wieder zur
ansicht zu bekommen aber das ging nicht :-( (war weg) screen -R.
Frage: werden mke2fs -c informationen im syslog abgelegt
beendet wurde. Alternativ kann man auch mit fsck herummurksen.
Während des Formatierens ist die ssh Verbindung abgebrochen.
Mit screen wollte ich versuchen den Dialog mke2fs -cj wieder zur
ansicht zu bekommen aber das ging nicht :-( (war weg) screen -R.
Der mke2fs-Prozess bekommt als Session
Hallo,
wie kann ich feststellen ob eine Partition fertig formatiert wurde oder
nicht?
Während des Formatierens ist die ssh Verbindung abgebrochen.
Mit screen wollte ich versuchen den Dialog mke2fs -cj wieder zur
ansicht zu bekommen aber das ging nicht :-( (war weg) screen -R.
Frage: werden
Bonjour,
Sans faire attention j'ai fais un mke2fs sur une
des mes partitions, je souhaite la récupérer.
J'ai cherché sur Internet mais je ne trouve pas de
méthode simple c'est à dire sans avoir à supprimer
toutes mes partition pour les
re-créer.
merci d'avance pour votre aide
:-)
Selon Franck REY [EMAIL PROTECTED]:
| Bonjour,
'jour !
| Sans faire attention j'ai fais un mke2fs sur une des mes partitions,
| je souhaite la récupérer.
Erf... Dur. ÀMHA c'est déjà trop tard. Lire le howto Ext2fs
Undeletion.
| J'ai cherché sur Internet mais je ne trouve pas de
Bonjour,
Sans faire attention j'ai fais un mke2fs sur une
des mes partitions, je souhaite la récupérer.
J'ai cherché sur Internet mais je ne trouve pas de
méthode simple c'est à dire sans avoir à supprimer
toutes mes partition pour les
re-créer.
merci d'avance pour votre aide
:-)
Le jeudi 03 février 2005 à 16:34 +0100, Franck REY a écrit :
Bonjour,
Sans faire attention j'ai fais un mke2fs sur une des mes partitions,
je souhaite la récupérer.
J'ai cherché sur Internet mais je ne trouve pas de méthode simple
c'est à dire sans avoir à supprimer
toutes mes
hi
I tried to format a 40GB partition with mke2fs.
I typed:
mke2fs -b 4096 -i 4096 path to partition
After writing 135 of 12215 (or similar) tables the programm processes
very slow and was not finished after one hour formating... after one
hour it was on the 145 table.
Where is the problem
, je fais donc mon deuil des données non sauvegardées de la dite
partition et je la demonte et vas y que je te lui fais
un fdisk + destroy partoche + recreate partoche tout comme il faut
Je me dis meme qu'il vaut mieux rebooter apres le partitionnage.
Et là un petit mke2fs pour formater la partition
partitionnage.
Et là un petit mke2fs pour formater la partition. Et beh la, horreur
Kernel panic!!!
Je pense bien qu'il y a un pb hard sur la partition, encore que, mais
que 'Kernel panick' montre son bout du nez lors de ses manips de base me
trouble au plus haut point
bien bien bien, excellent conseil
que je m'en vais appliquer des ce soir
--
Boukhairi Abderahim
INRA BIA
0561285065
~*-,._.,-*~''~*-,._.,-*~''~HUMEUR,-*~''~*-,._.,-*~''~*-,._.,-*~
Si l'homme a été créé avant la femme, c'est pour pouvoir lui
permettre de placer quelques mots. Jules Renard
faut
Je me dis meme qu'il vaut mieux rebooter apres le partitionnage.
Et là un petit mke2fs pour formater la partition. Et beh la, horreur
Kernel panic!!!
Je pense bien qu'il y a un pb hard sur la partition, encore que, mais
que 'Kernel panick' montre son bout du nez lors de ses manips
the partition sizes don't matter,
only the number of partitions).
- Try to format a large partition (2G is OK, 20G is not) using
mke2fs.
A google search turned up a couple of mailing list posts suggesting
that this is a kernel bug which was fixed in an -ac patch at some
point, then reintroduced
Hi!
I was wondering what is used to detemine the maximum mount count in
mke2fs. I am told the default should be 20, but I've got (when
reformatting the same partition) a result of 24 and results of 31. Why
is this?
Thanks!
Sean Etc.
On 26-Nov 09:16, Sean Middleditch wrote:
Hi!
I was wondering what is used to detemine the maximum mount count in
mke2fs. I am told the default should be 20, but I've got (when
reformatting the same partition) a result of 24 and results of 31. Why
is this?
iirc, mke2fs tries to make
Invalid argument passed to ext2 library while setting up superblock
--i didn't get any response before, so i'm trying a different
--subject line. if this is the wrong place to ask, pliz direct
--me to the right one...
i tried the potato mke2fs on /dev/hda9 hda10 hda11, but only one
of the three
will trillich wrote:
Invalid argument passed to ext2 library while setting up superblock
--i didn't get any response before, so i'm trying a different
--subject line. if this is the wrong place to ask, pliz direct
--me to the right one...
i saw the last post but since noone has replied i
the potato mke2fs on /dev/hda9 hda10 hda11, but only one
of the three worked -- the other two bombed out with 'Invalid
argument passed to ext2 library while setting up superblock' ??
I recently had a similar problem. I my case it was /dev/hda4 (on a
10GB IBM), so I'm not sure whether it really
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
/dev/hda10: Invalid argument passed to ext2 library while setting up superblock
# mke2fs /dev/hda11
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
/dev/hda11: Invalid argument passed to ext2 library while setting up superblock
# mkfs.ext2
Why does 'mke2fs /dev/fd0' give
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
mke2fs: error in loading shared libraries: mke2fs: undefined symbol:
e2p_edit_feature
?
I've done a dist-upgrade but no juice.
-chris
On Wed, Jul 05, 2000 at 01:57:08PM -0400, Peter S Galbraith wrote:
This is weird.
On potato, running mke2fs wipes out the existing /etc/mtab file
(it's zero size) such that `df' and `mount' have no record of any
mounted filesystems.
Anyone else seen this?
No.
You can copy /proc/mounts
This is weird.
On potato, running mke2fs wipes out the existing /etc/mtab file
(it's zero size) such that `df' and `mount' have no record of any
mounted filesystems.
Anyone else seen this?
I use e.g. mke2fs -m 0 -i 16384 /dev/hda3
--
Peter Galbraith, research scientist [EMAIL
Hi, All
thanks for all the advices
indeed, it was sparse superblock feature which
prevents partition mounting with slink rescue.
thank you
OK
Hi, All
found strange problem with mke2fs on potato:
1. set new 20gig disk as /dev/hdb and created 2gig linux partition as
/dev/hdb1
2. running potato with kernel 2.2.14 on /dev/hda
3. run mke2fs on /dev/hdb1 mke2fs -c -m 0 /dev/hdb1 and it finished ok
4. was able to mount /dev/hdb1
/dev/hda6 779 804208813+ 83 Linux
/dev/hda7 805 932 1028128+ 83 Linux
/dev/hda8 933 1024738958+ 83 Linux
/dev/hda9 1025 1247 1791216 83 Linux
When I get to mke2fs -c /dev/hda8, I get the following error.
mke2fs 1.18
Hi,
I got a small used disk given to me that I am trying to put into a
small system I have. When I tried to run mke2fs on any of the partitions I
had created I get
Checking fro bad blocks (read-only test): Bad block 0 out of range;ignored.
done
Block 1 in primary superblock
partition after that.
G. Crimp wrote:
Hi,
I got a small used disk given to me that I am trying to put into a
small system I have. When I tried to run mke2fs on any of the partitions I
had created I get
Checking fro bad blocks (read-only test): Bad block 0 out of range;ignored
I suspect the drive is toast, but thought I would check first. Does
anyone know if a low level format or something else can save this, or is it
just garbage ?
Generally one bad block will come many, sooner or later. It is a defect
on the surface of the disk. However modern harddisks
Hi,
I've got a IBM PS/2 and tere were some problems with the harddik. I got
round this by creating the partions by hand. But I've got a problem: If
have to use mke2fs to install a file system and I know what to write for
parameters. (I'm a very unexperienced user)
Thanks,
Nils Sandmann
--
PGP
I'm trying to setup 4 4.51gig scsi drives.
I used the following to setup the drives:
(victor)[root:~#] mke2fs -c -v /dev/sda1
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
Linux ext2 filesystem format
Filesystem label=
1101824 inodes, 4401778 blocks
220088 blocks (5.00%) reserved
On Sun, 14 Dec 1997, matthew tebbens wrote:
Here is what 'df' says about the drives:
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hdb1 705433 485054 183942 73% /
/dev/sda14253289 509553 3523648 13% /var/sda1
This says I
On Sun, 14 Dec 1997, matthew tebbens wrote:
(victor)[root:~#] mke2fs -c -v /dev/sda1
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
Linux ext2 filesystem format
Filesystem label=
1101824 inodes, 4401778 blocks
220088 blocks (5.00%) reserved for the super user
First data block=1
Block
On Mon, 15 Dec 1997, David Wright wrote:
On Sun, 14 Dec 1997, matthew tebbens wrote:
(victor)[root:~#] mke2fs -c -v /dev/sda1
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
Linux ext2 filesystem format
Filesystem label=
1101824 inodes, 4401778 blocks
220088 blocks (5.00
On Mon, 15 Dec 1997, matthew tebbens wrote:
But I don't have 4,401,778 blocks, I only have a total of 4,253,289 blocks
which becomes aprox 4,355,367,000 bytes.
How does it get from 4,401,778 blocks to 4,253,289 blocks ?
Somewhere along the line I lost about 250,000 blocks... ??
You
Thats over 250megs of tables and internal structures ?
Wow...
On Mon, 15 Dec 1997, Scott Ellis wrote:
On Mon, 15 Dec 1997, matthew tebbens wrote:
But I don't have 4,401,778 blocks, I only have a total of 4,253,289 blocks
which becomes aprox 4,355,367,000 bytes.
How does it get
matthew tebbens wrote:
Thats over 250megs of tables and internal structures ?
Wow...
There is also 5% reserved for root, unless you specified otherwise
Tim
--
(work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps
The squeaky wheel gets the
Thats over 250megs of tables and internal structures ?
Wow...
Not only. I don't remeber whether it was already mentioned but by default
5% of the filesystem is reserved for the super-user. You may override
this default with -m option to mk2efs.
Alex Y.
On Mon, 15 Dec 1997, Scott Ellis
1101824 inodes, 4401778 blocks
220088 blocks (5.00%) reserved for the super user
/dev/sda14253289 13 4033188 0% /var/sdb1
/dev/sdb14253289 13 4033188 0% /var/sdb1
/dev/sdc14253289 13 4033188 0% /var/sdc1
/dev/sdd1
On Mon, 15 Dec 1997, matthew tebbens wrote:
On Mon, 15 Dec 1997, David Wright wrote:
On Sun, 14 Dec 1997, matthew tebbens wrote:
(victor)[root:~#] mke2fs -c -v /dev/sda1
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
Linux ext2 filesystem format
Filesystem label=
1101824
Hmmm interesting !
Thanks.
On Mon, 15 Dec 1997, David Wright wrote:
On Mon, 15 Dec 1997, matthew tebbens wrote:
On Mon, 15 Dec 1997, David Wright wrote:
On Sun, 14 Dec 1997, matthew tebbens wrote:
(victor)[root:~#] mke2fs -c -v /dev/sda1
mke2fs 1.10, 24-Apr-97 for EXT2
matthew tebbens [EMAIL PROTECTED] writes:
Here is what 'df' says about the drives:
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hdb1 705433 485054 183942 73% /
/dev/sda14253289 509553 3523648 13% /var/sda1
On Fri, 3 Oct 1997, Remco Blaakmeer wrote:
On Thu, 2 Oct 1997, David Stern wrote:
/usr/doc/util-linux/README.fdisk.gz says:
You can have up to 64 partitions on a single IDE disk, or up to 16
partitions on a single SCSI disk, at least as far as Linux is
concerned; in practice
to [EMAIL PROTECTED]
Since the program mke2fs existsts in the package e2fsprogs
__ dpkg -S mke2fs
e2fsprogs: /usr/man/man8/mke2fs.8.gz
e2fsprogs: /sbin/mke2fs
the bug report should be submitted on e2fsprogs.
The first two line of your mail message should be the name and
version
mke2fs existsts in the package e2fsprogs
__ dpkg -S mke2fs
e2fsprogs: /usr/man/man8/mke2fs.8.gz
e2fsprogs: /sbin/mke2fs
the bug report should be submitted on e2fsprogs.
The first two line of your mail message should be the name and
version of the programs you
On Thu, 2 Oct 1997, David Wright wrote:
On Wed, 1 Oct 1997, David Stern wrote:
[..Deleted stuff for brevity..]
Are you merely a stickler for detail, or does it concern you that
devices exist which have little (if any) practical use and are
potentially problematic?
Yes, I'm afraid
On Thu, 2 Oct 1997, David Stern wrote:
On Thu, 2 Oct 1997, David Wright wrote:
On Wed, 1 Oct 1997, David Stern wrote:
[..Deleted stuff for brevity..]
Are you merely a stickler for detail, or does it concern you that
devices exist which have little (if any) practical use and are
On Thu, 2 Oct 1997, David Stern wrote:
/usr/doc/util-linux/README.fdisk.gz says:
You can have up to 64 partitions on a single IDE disk, or up to 16
partitions on a single SCSI disk, at least as far as Linux is
concerned; in practice you will rarely want so many.
Maybe that's why
On Mon, 29 Sep 1997, Philippe Troin wrote:
On Mon, 29 Sep 1997 23:32:21 PDT David Stern ([EMAIL PROTECTED])
wrote:
I'm having an irregular experience with mke2fs. I'm attempting to
format /dev/sda16 and message says:
debian# mke2fs -v /dev/sda16
mke2fs 1.10, 24-Apr-97
On Tue, 30 Sep 1997, David Stern wrote:
On Mon, 29 Sep 1997, Philippe Troin wrote:
On Mon, 29 Sep 1997 23:32:21 PDT David Stern ([EMAIL PROTECTED])
wrote:
I tried changing the beginning and ending cylinders, to no avail. Why
does mke2fs think /dev/sda16 is the entire drive
On Wed, 1 Oct 1997, David Wright wrote:
On Tue, 30 Sep 1997, David Stern wrote:
On Mon, 29 Sep 1997, Philippe Troin wrote:
On Mon, 29 Sep 1997 23:32:21 PDT David Stern wrote:
I tried changing the beginning and ending cylinders, to no avail. Why
does mke2fs think /dev/sda16
Hi,
I'm having an irregular experience with mke2fs. I'm attempting to
format /dev/sda16 and message says:
debian# mke2fs -v /dev/sda16
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
/dev/sda16 is entire device, not just one partition!
Proceed anyway? (y,n)
But /dev/sda16 is just
On Mon, 29 Sep 1997 23:32:21 PDT David Stern ([EMAIL PROTECTED])
wrote:
I'm having an irregular experience with mke2fs. I'm attempting to
format /dev/sda16 and message says:
debian# mke2fs -v /dev/sda16
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
/dev/sda16 is entire device
On Mon, 29 Sep 1997, Philippe Troin wrote:
On Mon, 29 Sep 1997 23:32:21 PDT David Stern ([EMAIL PROTECTED])
wrote:
I'm having an irregular experience with mke2fs. I'm attempting to
format /dev/sda16 and message says:
debian# mke2fs -v /dev/sda16
mke2fs 1.10, 24-Apr-97
On Tue, 30 Sep 1997 00:16:12 PDT David Stern ([EMAIL PROTECTED])
wrote:
On Mon, 29 Sep 1997, Philippe Troin wrote:
Because /dev/sda16 has major 8, minor 16, which is the major/minor pair
for /dev/sdb: look at 'ls -l /dev/sda16 /dev/sdb'. BTW, you have
created sda16 yourself didn't you
mke2fs doesn't want to make a filesystem with block sizes other than 1024.
It claims I have a bad block 0. For example:
# mke2fs -c -b 4096 /dev/hda1
mke2fs 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
Linux ext2 filesystem format
Filesystem label=
130048
On Tue, 29 Jul 1997, Jesse Goldman wrote:
Hi,
From what I hear, there's a serious problem with that version of e2fsprogs
(at least fsck) which may be affecting your new file-system. Also, I
believe that 2 Gigs is the limit on a Linux filesystem's size so perhaps
that's causing you problems
Hi,
From what I hear, there's a serious problem with that version of e2fsprogs
(at least fsck) which may be affecting your new file-system. Also, I
believe that 2 Gigs is the limit on a Linux filesystem's size so perhaps
that's causing you problems as well...
J. Goldman
As someone who
Jim Pick wrote:
--==_Exmh_2089790933P
Content-Type: text/plain; charset=us-ascii
Hi,
From what I hear, there's a serious problem with that version of e2fsprogs
(at least fsck) which may be affecting your new file-system. Also, I
believe that 2 Gigs is the limit on a Linux
I just tried to partition my new hdisk (Quantum bigfoot 4.3 Gb) but I faced the
following problem:
- I created a 2.0 Gb primary partition with fdisk (cylinders 1 to 255)
- When I created the partition with mke2fs /dev/hdb1, it failed creating the
inode table with the following message:
Jul 29 23
Hi,
From what I hear, there's a serious problem with that version of e2fsprogs
(at least fsck) which may be affecting your new file-system. Also, I
believe that 2 Gigs is the limit on a Linux filesystem's size so perhaps
that's causing you problems as well...
J. Goldman
--
TO UNSUBSCRIBE FROM
On Tue, 29 Jul 1997 [EMAIL PROTECTED] wrote:
I just tried to partition my new hdisk (Quantum bigfoot 4.3 Gb) but I faced
the
following problem:
- I created a 2.0 Gb primary partition with fdisk (cylinders 1 to 255)
- When I created the partition with mke2fs /dev/hdb1, it failed creating
82 matches
Mail list logo
