problem then+i've got zero sized file in lost+found that i was unable
to delete until i took off all strange flash with chflags.
but i did it ONLY because i had no way to back it up.
Personally I don't think it's worth the risk, unless the data is
disposable like a squid cache. What I normally
On Wed, 16 Jan 2008 17:48:44 +0100 (CET)
Wojciech Puchar <[EMAIL PROTECTED]> wrote:
> growfs is for people that like challenges ;)
>
> i have to use it growing 800GB filesystem to 1400GB, finally (after
> patching it a bit) i did it, but root directory was destroyed (no
> idea why). all subdirs
(ffs_valloc: dup alloc). After plenty of 'fcsk -y' I got it fixed while
losing few random files. :( The errors were mostly related to soft updates.
Should soft updates be disabled before using growfs?
False alarm. It's all the same with soft updates disabled.. I guess growfs
needs some work.
Teemu Korhonen wrote:
I'm merging my ext2-partition with my /usr by shrinking ext2 and doing
growfs on the free space. I did it with soft updates enabled and it
seemed to work until I tried to use /usr which resulted in kernel
panic (ffs_valloc: dup alloc). After plenty of 'fcsk -y' I got it
f
and a long cold winter,
>
> Kris
>
>
> >From: Jerry McAllister <[EMAIL PROTECTED]>
> >To: Kristopher Yates <[EMAIL PROTECTED]>
> >CC: freebsd-questions@freebsd.org
> >Subject: Re: growfs HELP
> >Date: Thu, 28 Sep 2006 15:17:17 -0400
> >
]>
To: Kristopher Yates <[EMAIL PROTECTED]>
CC: freebsd-questions@freebsd.org
Subject: Re: growfs HELP
Date: Thu, 28 Sep 2006 15:17:17 -0400
On Thu, Sep 28, 2006 at 01:54:26PM -0500, Kristopher Yates wrote:
> Anyone else have any suggestions?
>
> I was thinking I could rewrite my p
D community for continuing to be the leader in
> backward-compatible support for old hardware. Long live the Pentium 60 and
> the 640 ATA controller! ;)
>
> Cheers,
>
> Kris
>
>
>
> >From: Jerry McAllister <[EMAIL PROTECTED]>
> >To: Kristopher Ya
ckward-compatible support for old hardware. Long live the Pentium 60 and
the 640 ATA controller! ;)
Cheers,
Kris
From: Jerry McAllister <[EMAIL PROTECTED]>
To: Kristopher Yates <[EMAIL PROTECTED]>
CC: freebsd-questions@freebsd.org
Subject: Re: growfs HELP
Date: Thu, 28 Sep 2006 11
On Thu, Sep 28, 2006 at 03:26:27AM -0500, Kristopher Yates wrote:
> Hi everyone,
>
> First of all, glad to still be running FBSD after all these years.
>
> I tried following some docs I found online in order to make my /usr
> partition bigger and made it all the way to growfs -s, which is where
Wojciech Puchar wrote:
i asked the question recently, no answers, but finally did it this way
and all worked fine. i shifted my partition left with dd and resized
with growfs.
Thanksgiving break may have taken at least some of the reading list population
out of regular contact, at least brief
Sorry for the double post but I found a copy of the actual error...
growfs: rdfs: seek error: 237231962044550260: Unknown error: 0
On Feb 20, 2005, at 2:40 AM, Michael Conlen wrote:
On FreeBSD 5.3 I added disks to a disk array. The array contained two
250 GB disks stripped (actually four mirrored
On Sep 29, 2004, at 4:56 AM, Kostya Falkov wrote:
#growfs -y /dev/vinum/bigger
...
bad inode number 1 to ginode
Where is the problem? At start partition was 432 GB, using step by step
growing(increasing -s option in growfs) I make 534GB and then I have
the same:
#growfs -y -s 1156529856 /dev/vunim/
>>> It has 'historical' reason. I started with vinum, when it was
>>> not possible to mirror root partition (at least I found just
>>> document 'Bootstrapping Vinum: A Foundation for Reliable
>>> Servers' by R. A. Van Valzah in 2001 or 2002 on
>>> www.freebsd.org)
>> Ther
>>> What you do now depends on the state of the file system.
>>> Hopefully you still have the original contents. In this case,
>> Yes, I have original contents. The volume size is 15GB just as
>> before.
> OK. You've seen le's message.
No. Probably, I missed it.
lk
___
At 2004-03-29T21:04:19Z, "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
> On Monday, 29 March 2004 at 18:38:20 +0200, Ludo Koren wrote:
>> It has 'historical' reason. I started with vinum, when it was not
>> possible to mirror root partition (at least I found just document
>> 'Bootstrapping Vi
On Monday, 29 March 2004 at 18:38:20 +0200, Ludo Koren wrote:
>
>
>>>
>>> vinum -> l ...
>>> D d1State: up /dev/da1s1e A: 0/15452 MB (0%)
>>> D rd1 State: up /dev/da1s1h A: 0/1023 MB (0%)
>
>> You shouldn't have more than one drive per spind
>>
>> vinum -> l ...
>> D d1State: up /dev/da1s1e A: 0/15452 MB (0%)
>> D rd1 State: up /dev/da1s1h A: 0/1023 MB (0%)
> You shouldn't have more than one drive per spindle.
It has 'historical' reason. I started with
On Mon, 29 Mar 2004, Greg 'groggy' Lehey wrote:
> On Monday, 29 March 2004 at 9:37:39 +0200, Ludo Koren wrote:
> > It finished with the following error:
> >
> > growfs: bad inode number 1 to ginode
> >
> > I have searched the archives, but did not find any answer. Please,
> > could you point to m
On Monday, 29 March 2004 at 9:37:39 +0200, Ludo Koren wrote:
>
>
> on 5.2.1-RELEASE-p3, I did:
>
> ...
> vinum create vinumgrow
>
> vinumgrow:
> drive d3 device /dev/da2s1h
> drive d4 device /dev/da3s1h
> sd name mirror.p0.s1 drive d3 plex mirror.p0 size 0
> sd name mirror.p1.s1 drive d4 plex mirr
On Monday, 23 February 2004 at 13:51:52 +1030, Michael Ritchie wrote:
> Greg 'groggy' Lehey wrote:
>> What file system? UFS 1 or UFS 2? growfs is suffering a bit from
>> lack of love at the moment. It might be worth putting in a PR.
>
> Thanks for the response,
>
> File system UFS2 (with softupd
Greg 'groggy' Lehey wrote:
What file system? UFS 1 or UFS 2? growfs is suffering a bit from
lack of love at the moment. It might be worth putting in a PR.
Thanks for the response,
File system UFS2 (with softupdates, if that matters?).
I've sort of worked around the issue at the moment (backed
On Sunday, 8 February 2004 at 21:43:19 +1030, Michael Ritchie wrote:
> I have followed the method advocated by Drew Tomlinson on this list
> (October 2002) to create a Vinum volume without losing data. Everything
> worked ok for the first drive... and then I added the second, and grew
> the file
+-Le 07/01/2004 13:30 +1030, Greg 'groggy' Lehey écrivait :
| On Tuesday, 6 January 2004 at 19:18:06 +0100, Mathieu Arnold wrote:
|> Ok, I could not wait, so I did :
|> a create with :
|> drive vinumdrive1 device /dev/ad3e
|> sd name data.p0.s1 drive vinumdrive1 len 0
|>
|> then :
|> attach data.
On Tuesday, 6 January 2004 at 19:18:06 +0100, Mathieu Arnold wrote:
> Ok, I could not wait, so I did :
> a create with :
> drive vinumdrive1 device /dev/ad3e
> sd name data.p0.s1 drive vinumdrive1 len 0
>
> then :
> attach data.p0.s1 data.p0
>
> That worked well, I had a 115GB volume, I now have a
> |# growfs /dev/vinum/data
> | We strongly recommend you to make a backup before growing the Filesystem
> |=20
> | Did you backup your data (Yes/No) ? Yes
> | new file systemsize is: 78997019 frags
> | growfs: wtfs: write error: 631976157: Inappropriate ioctl for device
> |=20
> | And well, it do
+-Le 06/01/2004 19:18 +0100, Mathieu Arnold écrivait :
| Ok, I could not wait, so I did :
| a create with :
| drive vinumdrive1 device /dev/ad3e
| sd name data.p0.s1 drive vinumdrive1 len 0
|
| then :
| attach data.p0.s1 data.p0
|
| That worked well, I had a 115GB volume, I now have a 301GB one
>
> Hey all...
>
> Have FreeBSD 4.8-STABLE, and I've run out of space on the slice /
>
> I really want to avoid having to backup and reformat, or doing anything
> that's super-time-intensive - from reading various posts and blogs
> related to FreeBSD, it appears to me that I can resolve my iss
On Sat, 13 Dec 2003 14:02:59 +1030
Malcolm Kay <[EMAIL PROTECTED]> probably wrote:
> On Sat, 13 Dec 2003 13:08, Jeff LaMarche wrote:
> > Hey all...
> >
> > Have FreeBSD 4.8-STABLE, and I've run out of space on the slice /
> >
> > I really want to avoid having to backup and reformat, or doing anyth
On Sat, 13 Dec 2003 13:08, Jeff LaMarche wrote:
> Hey all...
>
> Have FreeBSD 4.8-STABLE, and I've run out of space on the slice /
>
> I really want to avoid having to backup and reformat, or doing anything
> that's super-time-intensive - from reading various posts and blogs
> related to FreeBSD, i
Problems have been resolved, thanks again for the help =)
-Rishi
Sergey 'DoubleF' Zaharchenko wrote:
On Thu, 04 Dec 2003 14:23:13 -0800
Rishi Chopra <[EMAIL PROTECTED]> probably wrote:
I get:
growfs: we are not growing (1048576 -> 0)
So I took a look at your email, and you said:
"You've gr
In the last episode (Dec 04), Rishi Chopra said:
> Any idea why my partitions (da0s1a, da0s1d, da0s1e) don't have valid
> disk labels?
>
> # disklabel -A da0s1d | more
> disklabel: /dev/da0s1d: no valid label found
> # disklabel -A da0s1e | more
> disklabel: /dev/da0s1e: no valid label found
>
>
Any idea why my partitions (da0s1a, da0s1d, da0s1e) don't have valid
disk labels?
# disklabel -A da0s1d | more
disklabel: /dev/da0s1d: no valid label found
# disklabel -A da0s1e | more
disklabel: /dev/da0s1e: no valid label found
I created the partitions and mount points when installing the os us
In the last episode (Dec 04), Rishi Chopra said:
> Trying to enlarge a partition (/usr) on a slice (da0s1) with plenty of
> space:
>
> # fdisk
>
> The data for partition 1 is:
> sysid 165 (0xa5), (FreeBSD/NetBSD/386BSD)
>start 63, size 1171861362 (572197 Meg), flag 80 (active)
> beg: c
Scott Reese <[EMAIL PROTECTED]> writes:
> My old 20G drive in my 5.1-RELEASE box started to die last week, so I
> got a new drive (a 40G Seagate) and used Norton Ghost to copy over
> everything from the old drive to the new drive. At the moment, FreeBSD
> still thinks I've only got a 20G drive an
On Fri, 2003-08-08 at 17:51, Lowell Gilbert wrote:
> Scott Reese <[EMAIL PROTECTED]> writes:
>
> > My old 20G drive in my 5.1-RELEASE box started to die last week, so I
> > got a new drive (a 40G Seagate) and used Norton Ghost to copy over
> > everything from the old drive to the new drive. At th
35 matches
Mail list logo
