It wouldn't be the BSD way to try to stop the user shooting themselves
in the foot.
And I agree too as it wouldn't be right for glabel to try to keep
track of all possible uses for a volume and know whether each is
present.
That would be a typical Linux type solution.
However, would it be too much
On Mon, May 17, 2010 at 10:54:17PM +0930, Matt Thyer wrote:
> On 12 May 2010 11:16, Bernd Walter wrote:
> >
> > On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote:
> > > i've posted a log here which is pretty self explanatory:
> > >
> > > http://pastebin.com/tn3NiDDW
> > >
>
> [snip]
On 12 May 2010 11:16, Bernd Walter wrote:
>
> On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote:
> > i've posted a log here which is pretty self explanatory:
> >
> > http://pastebin.com/tn3NiDDW
> >
[snip]
>
> One of the typical problems users have is that they forget that
> adding
On Wed, May 12, 2010 at 3:46 AM, Bernd Walter wrote:
> On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote:
>> i've posted a log here which is pretty self explanatory:
>>
>> http://pastebin.com/tn3NiDDW
>>
>> On Tue, May 11, 2010 at 10:13 PM, Alexander Best
>> wrote:
>> > the problem i
On Tue, May 11, 2010 at 10:15:13PM +0200, Alexander Best wrote:
> i've posted a log here which is pretty self explanatory:
>
> http://pastebin.com/tn3NiDDW
>
> On Tue, May 11, 2010 at 10:13 PM, Alexander Best
> wrote:
> > the problem is getting more awkward.
> >
> > if i do `fsck /dev/label/root
i've posted a log here which is pretty self explanatory:
http://pastebin.com/tn3NiDDW
On Tue, May 11, 2010 at 10:13 PM, Alexander Best
wrote:
> the problem is getting more awkward.
>
> if i do `fsck /dev/label/rootfs` fsck complains that it cannot read a
> specific sector of my hdd as i mentione
the problem is getting more awkward.
if i do `fsck /dev/label/rootfs` fsck complains that it cannot read a
specific sector of my hdd as i mentioned before. if i run fsck on the
device node directly using `fsck /dev/ada0p3` however, fsck succeeds.
what i did was to boot into single user mode with /
On 3/29/10, Alexander Best wrote:
> hi there,
>
> when doing fsck on my / fs i get this error:
>
> "Cannot Read BLK. 471617640" and "The Following Disk Sectors could not be
> read: 471617643". after this message the partition gets marked dirty.
>
> i performed the following steps to verify the pro
hi there,
when doing fsck on my / fs i get this error:
"Cannot Read BLK. 471617640" and "The Following Disk Sectors could not be
read: 471617643". after this message the partition gets marked dirty.
i performed the following steps to verify the problem:
1) dd if=/dev/ada0 of=/dev/null bs=1m
2)
