Leslie Jensen writes:
> pkg version -vIL
> pkg: option requires an argument -- L
> usage: pkg version [-IPR] [-hoqv] [-l limchar] [-L limchar] [[-X] -s string]
> [-r reponame] [-O origin] [index]
> pkg version -t
> pkg version -T
&
I ran into a little problem with my "old" crontab scripts.
I do the following:
portsnap -I cron update
/usr/local/sbin/portmaster -y --clean-distfiles
/usr/local/sbin/portmaster -aF
pkg version -vIL
After changing to pkg the check for outdated ports fails on the -L flag
pkg ve
What should I do in this situation?
-- Eir Nym
On 28 April 2013 23:36, Eir Nym wrote:
> Since -l switch introduced into install(8), I can't build new FreeBSD
> box at all.
>
> I do following command set to build new box: (http://eroese.org/mkw.sh)
> 1) cd /usr/head/src
> From owner-freebsd-questi...@freebsd.org Mon Jun 18 09:25:32 2012
> Date: Mon, 18 Jun 2012 18:24:34 +0400
> From: Budnev Vladimir
> To: Mike Tancsa
> Cc: freebsd-questions@freebsd.org
> Subject: Re: (Free 7.2) "su -l" didnt prompt password.Is it possbile?
>
>
On 2012-06-18 16:41, Budnev Vladimir wrote:
The strange thing with possibly empty password is that login from
ip-console accepted correct password. So dont sure about empty...It
seems like su was accepting any password at that time.
That is the behavior with an empty password. The login would
r wrote:
>>
>>> And It looked such way:
>>>
>>> %su -l
>>>
>> Before you enter this command, post the output of
>> id
>>
> Unfortunately, we can not flashback or reproduce that step now, cause we'v
> hurried and changed root pass
18.06.2012 18:37, Mike Tancsa написал:
On 6/18/2012 10:24 AM, Budnev Vladimir wrote:
But mb you can point in what case there is possibility to make "su -l"
without any prompt.
If the uid is 0, you wont need to enter a passwd
Yeah i realized that you mean things came that way
On Mon, Jun 18, 2012 at 05:31:54PM +0400, Budnev Vladimir wrote:
> Hello everyone.
> We'v noticed some strange situation. After reboot and login, system
> didn't ask for password while switchig with su -l.
>
> In details, there was root login from terminal and one f
18.06.2012 18:32, Chris Rees ???:
On Jun 18, 2012 2:34 PM, "Budnev Vladimir" <mailto:vladimir.bud...@gmail.com>> wrote:
>
> Hello everyone.
> We'v noticed some strange situation. After reboot and login, system
didn't ask for password while switchig
On 6/18/2012 10:24 AM, Budnev Vladimir wrote:
> But mb you can point in what case there is possibility to make "su -l"
> without any prompt.
If the uid is 0, you wont need to enter a passwd
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex C
On Jun 18, 2012 2:34 PM, "Budnev Vladimir"
wrote:
>
> Hello everyone.
> We'v noticed some strange situation. After reboot and login, system
didn't ask for password while switchig with su -l.
>
> In details, there was root login from terminal and one from ssh.
&g
18.06.2012 18:02, Mike Tancsa написал:
On 6/18/2012 9:31 AM, Budnev Vladimir wrote:
And It looked such way:
%su -l
Before you enter this command, post the output of
id
Unfortunately, we can not flashback or reproduce that step now, cause
we'v hurried and changed root password to avoid
On 6/18/2012 9:31 AM, Budnev Vladimir wrote:
>
> And It looked such way:
>
> %su -l
Before you enter this command, post the output of
id
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet service
Hello everyone.
We'v noticed some strange situation. After reboot and login, system
didn't ask for password while switchig with su -l.
In details, there was root login from terminal and one from ssh.
Terminal login was directly as root(via ip-console), and ssh was as
user, the
>>> > The following creates a file with a size of 102402 (a gig)
>>> > fseek(stdout, 100*1024, SEEK_END);
>>> Nope :) What you have there is not actually called (anything).
>> It would maybe be called a MKiB. :-)
I'll buy that, if someone chips in the deuce :)
> In SI units it is called
On Thu, Jun 14, 2012 at 12:37 PM, Peter Vereshagin wrote:
> Hello.
>
> 2012/06/14 00:23:25 +0400 Peter Vereshagin => To
> freebsd-questions@freebsd.org:
>
> PV> ot the least how could I see the 'real' size of each of those files, both
> ~150M
> PV> actulally, with a system command?
>
> also, '
Hello.
2012/06/14 00:23:25 +0400 Peter Vereshagin => To
freebsd-questions@freebsd.org:
PV> ot the least how could I see the 'real' size of each of those files, both
~150M
PV> actulally, with a system command?
also, 'du' works that way for regular files. But implicitly I wanted about ls's
key
On Thu, 14 Jun 2012 08:40:27 +0100, Matthew Seaman wrote:
> On 14/06/2012 07:11, Polytropon wrote:
> > Even school taught that in the 80's: When dealing with
> > computers, 1 kB != 1000 B, but 1 kB = 1024 B. That is
> > considered basic knowledge.
>
> Schools teach a lot of things that are so glos
On 14/06/2012 08:40, Matthew Seaman wrote:
> Really? If I said the bandwidth usage was 10Mb/s would you immediately
> understand that was 10,000,000,000 bits per second?
Err... of course you wouldn't. 10,000,000 bits per second. That's what
I meant to type.
Matthew
--
Dr Matthew J Se
On 14/06/2012 07:11, Polytropon wrote:
> In IT context, already in the 60's and 70's, unit prefixes
> k, M and G always were interpreted as of 2^n (or 1024*),
> even if the unit was _words_, not bytes. :-)
Which was incorrect in principle
> Even school taught that in the 80's: When dealing with
>
On 13 June 2012 23:11, Polytropon wrote:
> On Wed, 13 Jun 2012 22:33:50 -0400, grarpamp wrote:
>> > The following creates a file with a size of 102402 (a gig)
>> > fseek(stdout, 100*1024, SEEK_END);
>>
>> Nope :) What you have there is not actually called (anything).
>
> It would maybe be
On Wed, 13 Jun 2012 22:33:50 -0400, grarpamp wrote:
> > The following creates a file with a size of 102402 (a gig)
> > fseek(stdout, 100*1024, SEEK_END);
>
> Nope :) What you have there is not actually called (anything).
It would maybe be called a MKiB. :-)
> A proper gibibyte = GiB =
> The following creates a file with a size of 102402 (a gig)
> fseek(stdout, 100*1024, SEEK_END);
Nope :) What you have there is not actually called (anything).
A proper gibibyte = GiB = 2^30 = 1024^3 = 1073741824
for data storage, ram (binary bit handling)
A proper gigabyte = GB = 1E9 =
What you have are sparse files. The size listed by ls -l is the
length of the files as if all the file from start to end contain data,
but unix allows one to seek beyond the end of a file and add more data,
thus leaving unused blocks. A common example of sparse files
is the *.pag file in a dbm
On 13 June 2012 16:23, Peter Vereshagin wrote:
> Hello.
>
> I have the directory in the file system with 2 regular files each of which
> is
> sized as 700M according to 'ls -l'. But the torrent client and 'du -s' and
> 'ls
> -l's '
Hi--
On Jun 13, 2012, at 1:23 PM, Peter Vereshagin wrote:
> I have the directory in the file system with 2 regular files each of which
> is
> sized as 700M according to 'ls -l'. But the torrent client and 'du -s' and
> 'ls
> -l's 'total&#
Hello.
I have the directory in the file system with 2 regular files each of which is
sized as 700M according to 'ls -l'. But the torrent client and 'du -s' and 'ls
-l's 'total' show that the directory size is 300M.
How can that be? Are there diffe
fact, I can readily mount the filesystem
if I do not specify "-L ...".
I did mount and then soon unmount the filesystem as root with "-L ...".
I see now. The loading of the kernel module is not permitted as I think the
mount command attempts to load it if necessary. I'm n
dan writes:
> On 10/29/10 01:00, Chuck Swiger wrote:
>> Hi, Dan--
>>
>> On Oct 28, 2010, at 3:45 PM, dan wrote:
>>> 'mount_msdosfs -L en_US.UTF-8 /dev/da0 local/mnt/'
>>>
>>> executed by a non root-user prints out the following
>
er
>>>> needs.
>>>>
>>>
>>>
>>> sysctl vfs.usermount=1
>>>
>>> Although it doesn't seem correct that you can mount that FS if it's
>>> already
>>> been mounted previously by root when that sysctl is at
lthough it doesn't seem correct that you can mount that FS if it's
>> already
>> been mounted previously by root when that sysctl is at 0.
>>
>>
> Hello
>
> vfs.usermount is already set. In fact, I can readily mount the filesystem
> if I do not specify "
't seem correct that you can mount that FS if it's already
been mounted previously by root when that sysctl is at 0.
Hello
vfs.usermount is already set. In fact, I can readily mount the
filesystem if I do not specify "-L ...".
I did mount and then soon unmount
On Fri, Oct 29, 2010 at 6:13 AM, dan wrote:
> Thank you for your research and prompt response. The module was available.
> I tried both: kldload in command line and adding it in loader.conf.
>
> Note. In case the module has not been been loaded,as a user, here, one gets
> 2 messages
> "mount_msdo
On 10/29/10 01:00, Chuck Swiger wrote:
Hi, Dan--
On Oct 28, 2010, at 3:45 PM, dan wrote:
'mount_msdosfs -L en_US.UTF-8 /dev/da0 local/mnt/'
executed by a non root-user prints out the following
"mount_msdosfs: msdosfs_iconv: Operation not permitted"
and then stops with
Hi, Dan--
On Oct 28, 2010, at 3:45 PM, dan wrote:
> 'mount_msdosfs -L en_US.UTF-8 /dev/da0 local/mnt/'
>
> executed by a non root-user prints out the following
>
> "mount_msdosfs: msdosfs_iconv: Operation not permitted"
>
> and then stops with error 71
Hello :-)
'mount_msdosfs -L en_US.UTF-8 /dev/da0 local/mnt/'
executed by a non root-user prints out the following
"mount_msdosfs: msdosfs_iconv: Operation not permitted"
and then stops with error 71 on console.
Later, the same command, executed by the same user, complete
Hello :-)
'mount_msdosfs -L en_US.UTF-8 /dev/da0 local/mnt/'
executed by a non root-user prints out the following
"mount_msdosfs: msdosfs_iconv: Operation not permitted"
and then stops with error 71 on console.
Later, the same command, executed by the same user, complete
86b6fc16926168e N/A ad4s1f
> >>
> >> Local:
> >>
> >> [st...@fyre /usr/home/steve]$ glabel status
> >> Name Status Components
> >> iso9660/WALL_E N/A acd0
> >> [st...@fyre /usr/home/steve]$
> >>
> >
abel status
>> Name Status Components
>> ufsid/486b6fc38d330916 N/A ad4s1d
>> ufsid/486b6fc16926168e N/A ad4s1f
>>
>> Local:
>>
>> [st...@fyre /usr/home/steve]$ glabel status
>> Name Status Components
>> i
68e N/A ad4s1f
>
> Local:
>
> [st...@fyre /usr/home/steve]$ glabel status
> Name Status Components
> iso9660/WALL_E N/A acd0
> [st...@fyre /usr/home/steve]$
>
I don't see anything here either on my system.
Doesn't tunefs -L work?
Wait a second. What do I have to do, mount single user to find the
darn things? They have completely disappeared, not even a
'GEOM_LABEL: Label ufsid/482b3a7c20b36d8c removed' in dmesg! (thought
I was previously seeing that on shutdown, not startup, now neither)
Even in single user mode, root is
On Sun, Mar 14, 2010 at 09:31:50AM -0700, Steve Franks wrote:
> I'm seeing this in my dmesg:
>
> GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s).
AFAICT, you can ignore this. There have been previous discussions of this on
the mailing list.
> I'm guessing
I'm seeing this in my dmesg:
GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s).
I'm guessing I screwed up tunefs -L, but it sure looked
straightforward. Anyway, my /dev/ufs is empty, and I kind of thought
there should be stuff in it. I called tunefs -L from single-use
Hi all:
Did the portupgrade and a certain number of applications failed due to the
error:
gcc: /usr/local/lib/libgssapi.so: No such file or directory
but i look at the file and it does exist:
hm_1# ls -al /usr/local/lib/libgssapi.so
lrwxr-xr-x 1 root wheel 14 Feb 7 20:48 /usr/local/lib/li
clean out
kde4 -- which i tried months ago. but parts got messed up with other
version-4 apps like qt4-*. i'm rebuilding "tao" with portmanager -i -p
-l
which, according to my howto notes, will fix broken dependencies. is
theran
analogue m
Steve Polyack skrev:
Roger Olofsson wrote:
Dear mailing list,
What would be the correct way to do the following:
mount_nfs -L server:/path mnt
when using the /etc/fstab file?
Greetings from Sweden
/Roger
Any options passed to mount(8)may be added (comma separated) to the
Options
Roger Olofsson wrote:
Dear mailing list,
What would be the correct way to do the following:
mount_nfs -L server:/path mnt
when using the /etc/fstab file?
Greetings from Sweden
/Roger
Any options passed to mount(8)may be added (comma separated) to the
Options section in /etc/fstab.
For
Dear mailing list,
What would be the correct way to do the following:
mount_nfs -L server:/path mnt
when using the /etc/fstab file?
Greetings from Sweden
/Roger
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman
> > > (sorry for the big paste):
> > >
> > > ghirai# portsclean -L
> > > ** /usr/local/lib/libcharset.so.1 is shadowed by
> > > /usr/X11R6/lib/libcharset.so.1 /usr/X11R6/lib/libcharset.so.1
> > > <- libiconv-1.11_1
> > > /usr/local/lib/l
On Tue, 24 Jun 2008 07:13:51 -0500
David J Brooks <[EMAIL PROTECTED]> wrote:
> On Tuesday 24 June 2008 04:41:55 am Ghirai wrote:
> > After upgrading couple ports, i get this output with portsclean
> > (sorry for the big paste):
> >
> > ghirai# portsclean -L
>
On Tuesday 24 June 2008 04:41:55 am Ghirai wrote:
> After upgrading couple ports, i get this output with portsclean (sorry for
> the big paste):
>
> ghirai# portsclean -L
> ** /usr/local/lib/libcharset.so.1 is shadowed by
> /usr/X11R6/lib/libcharset.so.1 /usr/X11R6/l
After upgrading couple ports, i get this output with portsclean (sorry for the
big paste):
ghirai# portsclean -L
** /usr/local/lib/libcharset.so.1 is shadowed by /usr/X11R6/lib/libcharset.so.1
/usr/X11R6/lib/libcharset.so.1 <- libiconv-1.11_1
/usr/local/lib/libcharset.s
On Thu, May 8, 2008 at 1:53 PM, RW <[EMAIL PROTECTED]> wrote:
>> How to do unattended ports upgrade? I am using FreeBSD 7.0 and
>> portmanager ask me strange questions[0] (about compile-time options)
>
> It's not actually portmanager, it's the ports-system itself. This
> question comes-up regularly
On Thu, May 8, 2008 at 2:10 PM, Simon Jolle <[EMAIL PROTECTED]> wrote:
> Hi FreeBSD users
>
> How to do unattended ports upgrade? I am using FreeBSD 7.0 and
> portmanager ask me strange questions[0] (about compile-time options)
Unattended?
Even on Windows, I doubt they do that:-)
--
Best rega
On Thu, 8 May 2008 13:10:23 +0200
"Simon Jolle" <[EMAIL PROTECTED]> wrote:
> Hi FreeBSD users
>
> How to do unattended ports upgrade? I am using FreeBSD 7.0 and
> portmanager ask me strange questions[0] (about compile-time options)
It's not actually portmanager, it's the ports-system itself. Thi
Hi FreeBSD users
How to do unattended ports upgrade? I am using FreeBSD 7.0 and
portmanager ask me strange questions[0] (about compile-time options)
cheers
Simon
[0] http://img384.imageshack.us/img384/8657/portmanageruloptionsaw9.png
--
XMPP: [EMAIL PROTECTED]
__
rk Evans" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, December 13, 2007 12:22 PM
Subject: Re: ls -l takes a forever to finish.
On Wed, 12 Dec 2007 13:28:23 -0600
"Mark Evans" <[EMAIL PROTECTED]> wrote:
this program seems to have the same issues wi
and sorts its output
externally with another sorting algorithm. sortls.py speeds
up "ls -l" considerably for huge (10,000+ entries) directories
by using another sorting algorithm, it doesn't do anything else.
Just to ask again: while you're waiting for "ls -lf",
ark Evans" <[EMAIL PROTECTED]>
Sent: Thursday, November 29, 2007 8:42 AM
Subject: Re: ls -l takes a forever to finish.
On Thu, 29 Nov 2007 08:42:44 -0500
Bill Moran <[EMAIL PROTECTED]> wrote:
In response to Wojciech Puchar <[EMAIL PROTECTED]>:
> > ls | wc
>
&g
On Fri, Nov 30, 2007 at 05:49 ,
[EMAIL PROTECTED] moved his mouse, rebooted
for the change to take effect, and then said:
> Date: Thu, 29 Nov 2007 08:42:44 -0500
> From: Bill Moran <[EMAIL PROTECTED]>
> Subject: Re: ls -l takes a forever to finish.
> In response to Wojci
the fix would be
mv /usr/home /usr/oldhome;mkdir /usr/home;mv /usr/oldhome/* /usr/home
and after successfull move - rm -rf /usr/home
I like this idea very much...
It results in 100% data loss of your /usr/home contents...
;-)
___
freebsd-questions@f
>
> it is for sure.
>
> the fix would be
>
> mv /usr/home /usr/oldhome;mkdir /usr/home;mv /usr/oldhome/* /usr/home
>
> and after successfull move - rm -rf /usr/home
I really hope you meant: rm -rf /usr/oldhome
Also, mv just moves pointers around, wouldn't a cp -Rp be needed instead?
_
I guess that replacing qsort(3) in
/usr/src/lib/libc/gen/fts.c:fts_sort()
with another sort algorithm which doesn't
expose this anomaly would solve that problem.
for sure his /home wasn't worst case. it's just average case so it's not
that problem.
unless you have 486/33 or slower system there is something wrong.
Another possible scenario is that the directory is badly fragmented.
Unless something has changed since I last researched this (which is
it is for sure.
the fix would be
mv /usr/home /usr/oldhome;mkdir /usr/home;mv /usr/oldhom
ls takes 0.1 seconds user time, ls -l takes 0.3 second user time.
unless you have 486/33 or slower system there is something wrong.
Has anyone tried fsck and/or smartmontools on the drive? Maybe something
like Spinrite?
he stated that CPU load is near 100% so it's not disk pr
; $a;a=$[a+1];done
> >
> > completed <25 seconds on 1Ghz CPU
> >
> > ls takes 0.1 seconds user time, ls -l takes 0.3 second user time.
> >
> > unless you have 486/33 or slower system there is something wrong.
>
> Another possible scenario is that th
In response to Wojciech Puchar <[EMAIL PROTECTED]>:
> > ls | wc
>
> strange. i did
>
> [EMAIL PROTECTED] ~/b]$ a=0;while [ $a -lt 1 ];do mkdir $a;a=$[a+1];done
>
> completed <25 seconds on 1Ghz CPU
>
> ls takes 0.1 seconds user time, ls -l takes 0.3
Wojciech Puchar wrote:
ls | wc
strange. i did
[EMAIL PROTECTED] ~/b]$ a=0;while [ $a -lt 1 ];do mkdir $a;a=$[a+1];done
completed <25 seconds on 1Ghz CPU
ls takes 0.1 seconds user time, ls -l takes 0.3 second user time.
unless you have 486/33 or slower system there is something wr
ls | wc
strange. i did
[EMAIL PROTECTED] ~/b]$ a=0;while [ $a -lt 1 ];do mkdir $a;a=$[a+1];done
completed <25 seconds on 1Ghz CPU
ls takes 0.1 seconds user time, ls -l takes 0.3 second user time.
unless you have 486/33 or slower system there is something wr
Is a partition close to full, use df to see that.
doesn't matter as ls read, not writes.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Wed, 28 Nov 2007 09:44:03 -0600
"Mark Evans" <[EMAIL PROTECTED]> wrote:
> No we are not using NIS.
>
> it is a large directory i am listing. actually it is the /usr/home
> directory, and is probably the largest on the system. However "ls -l"
> runs
ls | wc
returns " 88368836 71583"
Thanks
Mark
- Original Message -
From: Jeff Mohler
To: Mark Evans
Cc: [EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 9:52 AM
Subject: Re: ls -l takes a forever to finish.
HOW large is the directory?
On Wed, 2007-11-28 at 09:44 -0600, Mark Evans wrote:
> No we are not using NIS.
>
> it is a large directory i am listing. actually it is the /usr/home
> directory, and is probably the largest on the system. However "ls -l" runs
> for close to six minutesand spends the
HOW large is the directory?
ls | wc -l
On Nov 28, 2007 7:44 AM, Mark Evans <[EMAIL PROTECTED]> wrote:
> No we are not using NIS.
>
> it is a large directory i am listing. actually it is the /usr/home
> directory, and is probably the largest on the system. However "ls
No we are not using NIS.
it is a large directory i am listing. actually it is the /usr/home
directory, and is probably the largest on the system. However "ls -l" runs
for close to six minutesand spends the 10 seconds scrolling the screen with
the results. so i wait ls to start s
find no aliease for "ls -l"
df returns the following. So looks like there is restill about 40 G on the
partition.
ilesystem SizeUsed Avail Capacity Mounted on
/dev/aacd0s1a 97G 57G 33G64%/
devfs1.0K1.0K 0B 100%
Mark Evans wrote:
I'm using FreeBSD 6.1-RELEASE. When I run "ls -l" it takes forever for the it to complete. top
shows that the "ls -l" command uses about 98% of the CPU doing the time. If I run "ls"
I do not experience any problem. anyone have any ideas?
Is a partition close to full, use df to see that.
Is ls -l aliased to something else that is digging into your directory
tree, like when you're in /usr and type du?
brian
On Tue, 27 Nov 2007, Mark Evans wrote:
I'm using FreeBSD 6.1-RELEASE. When I run "ls -l" it takes f
On Nov 27, 2007, at 1:53 PM, Mark Evans wrote:
I'm using FreeBSD 6.1-RELEASE. When I run "ls -l" it takes forever
for the it to complete. top shows that the "ls -l" command uses
about 98% of the CPU doing the time. If I run "ls" I do not
experience
I'm using FreeBSD 6.1-RELEASE. When I run "ls -l" it takes forever for the it
to complete. top shows that the "ls -l" command uses about 98% of the CPU doing
the time. If I run "ls" I do not experience any problem. a
On Wed, Oct 24, 2007 at 02:39:16AM +0200, Johan Andersson wrote:
> Hello..
> Anyone know if motherboard MSI P4M900M2-L with the chip VT8237A works
> with FreeBSD 6.2 amd64?
> Do all the stuff works like p-ata/s-ata controller and network card work?
>
> im going to build a smal
Hello..
Anyone know if motherboard MSI P4M900M2-L with the chip VT8237A works
with FreeBSD 6.2 amd64?
Do all the stuff works like p-ata/s-ata controller and network card work?
im going to build a small server with that motherboard.
Need to know if it works with FreeBSD before i buy it :)
Thanks
> >
> >[EMAIL PROTECTED] ~] snapinfo -v /home
> >/dev/ad0s2f mounted on /home
> >no snapshots found
> >[EMAIL PROTECTED] ~] ll /home/.snap/
> >total 0
> >[EMAIL PROTECTED] ~]
> >
> >
> >Is this normal? Does it mean that dump is not r
[EMAIL PROTECTED] ~] ll /home/.snap/
total 0
[EMAIL PROTECTED] ~]
Is this normal? Does it mean that dump is not really dumping a
snapshot though it says it is?
man dump (the section regarding -L) says
"The snapshot is unlinked as soon as the dump starts, and is thus
removed when the du
Colleagues,
Right now I am watching a dump:
[EMAIL PROTECTED] ~] dump -b64 -5Lau /home
DUMP: Connection to big.sibptus.tomsk.ru established.
DUMP: Date of this level 5 dump: Sat Aug 18 14:02:16 2007
DUMP: Date of last level 0 dump: Sun Aug 12 11:10:56 2007
DUMP: Dumping snapshot of /dev/a
"expected next file 12345, got 23456"
I'm seeing this too. It's always exactly one inode per file system.
not one, sometimes even tens.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To uns
I always use "dump -L" to dump a live filesystem.
However, when I restore the dump, I sometimes get messages like
"foo.txt (inode 12345) not found on tape" or
"expected next file 12345, got 23456"
i had it too, sometimes even restore is unable to restore well -1-
On 07/08/07, Victor Sudakov <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > > > > > > Does nobody know the answer, or am I the only one experiencing the
> > > > > > > problem?
> > > > > >
> > > > > > I don't know the answer, but I get essentially the
> > > > > > same behaviour. I hav
[EMAIL PROTECTED] wrote:
>
> > > > > > Does nobody know the answer, or am I the only one experiencing the
> > > > > > problem?
> > > > >
> > > > > I don't know the answer, but I get essentially the
> > > > > same behaviour. I have never seen any data loss,
> > > >
> > > > I gave an example below.
On 06/08/07, Victor Sudakov <[EMAIL PROTECTED]> wrote:
> > > > > Does nobody know the answer, or am I the only one experiencing the
> > > > > problem?
> > > >
> > > > I don't know the answer, but I get essentially the
> > > > same behaviour. I have never seen any data loss,
> > >
> > > I gave an
cpghost wrote:
> > > > > I always use "dump -L" to dump a live filesystem.
> > > > > However, when I restore the dump, I sometimes get messages like
> > > > > "foo.txt (inode 12345) not found on tape" or
> > > > >
Jerry McAllister wrote:
>
> > Victor Sudakov wrote:
> > >
> > > I always use "dump -L" to dump a live filesystem.
> > > However, when I restore the dump, I sometimes get messages like
> > > "foo.txt (inode 12345) not found on tape&quo
Bill Moran wrote:
> > > Here is another example:
> > >
> > > [EMAIL PROTECTED] ~] restore -b64 -rN
> > > ./spool/samba.lock/wins.dat: (inode 2829098) not found on tape
> > > expected next file 267, got 4
> > > expected next file 2828988, got 2828987
[dd]
>
> My guess would be that something is
In response to Jerry McAllister <[EMAIL PROTECTED]>:
> On Mon, Aug 06, 2007 at 09:56:15AM +0700, Victor Sudakov wrote:
>
> > Victor Sudakov wrote:
> > >
> > > I always use "dump -L" to dump a live filesystem.
> > > However, when I restore
On Mon, Aug 06, 2007 at 09:56:15AM +0700, Victor Sudakov wrote:
> Victor Sudakov wrote:
> >
> > I always use "dump -L" to dump a live filesystem.
> > However, when I restore the dump, I sometimes get messages like
> > "foo.txt (inode 12345) not found
On Mon, Aug 06, 2007 at 02:18:57PM +0700, Victor Sudakov wrote:
> > > > I always use "dump -L" to dump a live filesystem.
> > > > However, when I restore the dump, I sometimes get messages like
> > > > "foo.txt (inode 12345) not found on ta
[EMAIL PROTECTED] wrote:
> > >
> > > I always use "dump -L" to dump a live filesystem.
> > > However, when I restore the dump, I sometimes get messages like
> > > "foo.txt (inode 12345) not found on tape" or
> > > "expected
On 05/08/07, Victor Sudakov <[EMAIL PROTECTED]> wrote:
> Victor Sudakov wrote:
> >
> > I always use "dump -L" to dump a live filesystem.
> > However, when I restore the dump, I sometimes get messages like
> > "foo.txt (inode 12345) not found on t
Victor Sudakov wrote:
>
> I always use "dump -L" to dump a live filesystem.
> However, when I restore the dump, I sometimes get messages like
> "foo.txt (inode 12345) not found on tape" or
> "expected next file 12345, got 23456"
>
> I thought
259101 ./usr/share/tmac/m.tmac
$ restore -tvf test.dmp | grep " 11"
Level 0 dump of / on test.sibptus.tomsk.ru:/dev/ad0s1a
Label: none
dir1130496 ./media
$
This means that
1. "/var/db/entropy/saved-entropy.1" was not dumped for some reason, though
"-L" was giv
1 - 100 of 187 matches
Mail list logo
